Kernel warning or panic via unlocked BPF parser
Published Sep 17, 2026 · Updated Sep 18, 2026
Missing RCU locking in the Linux KCM strparser allows local users to trigger a kernel warning through BPF map operations. kcm_parse_func_strparser() pins execution to a CPU but runs the BPF program without entering an RCU read-side critical section, so map operations fail the bpf_rcu_lock_held() assertion. Triggering requires a KCM strparser BPF program that performs map operations; systems configured with panic_on_warn crash instead of only logging the warning.
Summary
What happened
Missing RCU locking in the Linux KCM strparser allows local users to trigger a kernel warning through BPF map operations. kcm_parse_func_strparser() pins execution to a CPU but runs the BPF program without entering an RCU read-side critical section, so map operations fail the bpf_rcu_lock_held() assertion. Triggering requires a KCM strparser BPF program that performs map operations; systems configured with panic_on_warn crash instead of only logging the warning.
The record
- CVE
- CVE-2026-90143
- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.9
- Affected versionversion=9b73896a81dc68a638a011877b7344b252f92276 <1d26a6e007d46babc7fa76e5a157dccf86cd55c0
- Affected versionversion=9b73896a81dc68a638a011877b7344b252f92276 <21526f8a191a3c50622b8c10bd927870d780eae4
- Affected versionversion=9b73896a81dc68a638a011877b7344b252f92276 <292846223eaddba890e40699d2ab82ee5671798c
- Affected versionversion=9b73896a81dc68a638a011877b7344b252f92276 <37108861cf7bd909d4a372069bcd61c8f489e232
- Affected versionversion=9b73896a81dc68a638a011877b7344b252f92276 <3c70d27e792a28bca650ddd8a9aa0fe3591ffec5
- Affected versionversion=9b73896a81dc68a638a011877b7344b252f92276 <b0346dd64e4905291cc9c479f2e6cf1884ced4e6
- Affected versionversion=9b73896a81dc68a638a011877b7344b252f92276 <b0e94ea63dbdcbfec9beb819cd5f8fa584809ef2
- Affected versionversion=9b73896a81dc68a638a011877b7344b252f92276 <f392affef3c9ce64dfdde794df0579e0a7793440
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started