net: kcm: Hold RCU read lock while running BPF parser
In the Linux kernel, the following vulnerability has been resolved: net: kcm: Hold RCU read lock while running BPF parser kcm_parse_func_strparser() calls bpf_prog_run_pin_on_cpu() which prevents CPU migration, but does not establish an RCU read-side critical section. Consequently, BPF map operations can trigger WARN_ON_ONCE(!bpf_rcu_lock_held()) when called from the KCM strparser program. Hold the RCU read lock while running the program.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- EPSS
- 0.2% · 6th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.9affected
- 9b73896a81dc68a638a011877b7344b252f92276 and later · before 37108861cf7bd909d4a372069bcd61c8f489e232affected · git
- 9b73896a81dc68a638a011877b7344b252f92276 and later · before 3c70d27e792a28bca650ddd8a9aa0fe3591ffec5affected · git
- 9b73896a81dc68a638a011877b7344b252f92276 and later · before 1d26a6e007d46babc7fa76e5a157dccf86cd55c0affected · git
- 9b73896a81dc68a638a011877b7344b252f92276 and later · before b0e94ea63dbdcbfec9beb819cd5f8fa584809ef2affected · git
- 9b73896a81dc68a638a011877b7344b252f92276 and later · before 21526f8a191a3c50622b8c10bd927870d780eae4affected · git
- 9b73896a81dc68a638a011877b7344b252f92276 and later · before 292846223eaddba890e40699d2ab82ee5671798caffected · git
- 9b73896a81dc68a638a011877b7344b252f92276 and later · before f392affef3c9ce64dfdde794df0579e0a7793440affected · git
- 9b73896a81dc68a638a011877b7344b252f92276 and later · before b0346dd64e4905291cc9c479f2e6cf1884ced4e6affected · git
- before 4.9not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | all versions | — |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1d26a6e007d46babc7fa76e5a157dccf86cd55c0 | Vendor (CNA) |
| Linux Linux | 21526f8a191a3c50622b8c10bd927870d780eae4 | Vendor (CNA) |
| Linux Linux | 292846223eaddba890e40699d2ab82ee5671798c | Vendor (CNA) |
| Linux Linux | 37108861cf7bd909d4a372069bcd61c8f489e232 | Vendor (CNA) |
| Linux Linux | 3c70d27e792a28bca650ddd8a9aa0fe3591ffec5 | Vendor (CNA) |
| Linux Linux | b0346dd64e4905291cc9c479f2e6cf1884ced4e6 | Vendor (CNA) |
| Linux Linux | b0e94ea63dbdcbfec9beb819cd5f8fa584809ef2 | Vendor (CNA) |
| Linux Linux | f392affef3c9ce64dfdde794df0579e0a7793440 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/1d26a6e007d46babc7fa76e5a157dccf86cd55c0
- git.kernel.org/stable/c/21526f8a191a3c50622b8c10bd927870d780eae4
- git.kernel.org/stable/c/292846223eaddba890e40699d2ab82ee5671798c
- git.kernel.org/stable/c/37108861cf7bd909d4a372069bcd61c8f489e232
- git.kernel.org/stable/c/3c70d27e792a28bca650ddd8a9aa0fe3591ffec5
- git.kernel.org/stable/c/b0346dd64e4905291cc9c479f2e6cf1884ced4e6
- git.kernel.org/stable/c/b0e94ea63dbdcbfec9beb819cd5f8fa584809ef2
- git.kernel.org/stable/c/f392affef3c9ce64dfdde794df0579e0a7793440
Vendor advisories and official records. Exploit/PoC links are deliberately left out.