PatchSiren cyber security CVE debrief
CVE-2026-90143 Linux CVE debrief
A vulnerability in the Linux kernel's kcm_parse_func_strparser() function has been resolved. The function calls bpf_prog_run_pin_on_cpu(), which prevents CPU migration but does not establish an RCU read-side critical section. This can trigger WARN_ON_ONCE(!bpf_rcu_lock_held()) when BPF map operations are called from the KCM strparser program. To fix this, the RCU read lock should be held while running the BPF parser.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- HIGH 7.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-17
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-09-17
- Advisory updated
- 2026-09-18
Who should care
Linux kernel developers and maintainers, Linux distribution vendors, and users of Linux-based systems should assess exposure and apply the patch or mitigation measures as needed. They should verify Linux kernel patch application to prevent WARN_ON_ONCE(!bpf_rcu_lock_held()) errors and monitor system logs for errors related to BPF map operations. Additionally, they should review compensating controls for exposed systems while remediation is scheduled and
Why it matters
A Linux kernel vulnerability can cause WARN_ON_ONCE(!bpf_rcu_lock_held()) errors when BPF map operations are called from the KCM strparser program. Linux kernel developers, maintainers, and users should assess exposure and apply the patch or mitigation measures as needed.
- Verify Linux kernel patch application to prevent WARN_ON_ONCE(!bpf_rcu_lock_held()) errors.
- Assess Linux kernel version and configuration to ensure patch applicability.
- Monitor system logs for errors related to BPF map operations.
Technical summary
The Linux kernel's kcm_parse_func_strparser() function has a vulnerability that can trigger WARN_ON_ONCE(!bpf_rcu_lock_held()) errors when BPF map operations are called from the KCM strparser program. The fix involves holding the RCU read lock while running the BPF parser. This vulnerability affects Linux kernel developers and maintainers, Linux distribution vendors, and users of Linux-based systems. The technical impact is medium, and the fix requires patching the Linux kernel to establish an RCU read-side critical section.
Defensive priority
Medium
Recommended defensive actions
- Review and apply the Linux kernel patch to hold the RCU read lock while running the BPF parser.
- Verify the Linux kernel version and configuration to ensure the patch is applied correctly.
- Monitor system logs for WARN_ON_ONCE(!bpf_rcu_lock_held()) errors.
- Assess Linux kernel version and configuration to ensure patch applicability.
- Verify Linux kernel patch application to prevent WARN_ON_ONCE(!bpf_rcu_lock_held()) errors.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
Evidence notes
The CVE record and NVD vulnerability detail page provide information about the vulnerability. The Linux kernel patch notes and Git commit hashes are also available. To verify, defenders should check the Linux kernel version and configuration to ensure the patch is applied correctly and monitor system logs for WARN_ON_ONCE(!bpf_rcu_lock_held()) errors. Additionally, they should assess exposure and apply the patch or mitigation measures as needed. Evidence is limited to public sources and may not reflect all affected systems or specific
Sources and references
Verified primary and authoritative sources
-
CVE-2026-90143 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-90143
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-90143 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-90143
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/1d26a6e007d46babc7fa76e5a157dccf86cd55c0
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/21526f8a191a3c50622b8c10bd927870d780eae4
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/292846223eaddba890e40699d2ab82ee5671798c
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/37108861cf7bd909d4a372069bcd61c8f489e232
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/3c70d27e792a28bca650ddd8a9aa0fe3591ffec5
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/b0346dd64e4905291cc9c479f2e6cf1884ced4e6
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/b0e94ea63dbdcbfec9beb819cd5f8fa584809ef2
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/f392affef3c9ce64dfdde794df0579e0a7793440
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.