bpf: Fix stack slot index in nospec checks
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 4.20, 475405593de2b796224c6297aece44f321195919, 5.10.261.
Low priority for now. Upgrade to Linux Linux 4.20, 475405593de2b796224c6297aece44f321195919, 5.10.261 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix stack slot index in nospec checks check_stack_write_fixed_off() computes the byte slot for a fixed-offset stack write as -off - 1, and records each written byte in slot_type[] with (slot - i) % BPF_REG_SIZE. The Spectre v4 sanitization pre-check uses slot_type[i] instead. For a 4-byte write at fp-8 after the lower half of fp-8 has been zeroed, the pre-check scans bytes 0..3 and sees STACK_ZERO while the actual write updates bytes 7..4. That can leave the second half-slot write without nospec_result even though the bytes being overwritten still require sanitization. Use the same slot index in the sanitization pre-check that the write path uses when updating slot_type[].
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
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
- 872968502114d68c21419cf7eb5ab97717e7b803, f5893af2704eb763eb982f01d573f5b19f06b623, 0b27bdf02c400684225ee5ee99970bcbf5082282, 5.14affected
- 0e9280654aa482088ee6ef3deadef331f5ac5fb0 and later · before e62268e695075a481a6c4feeb022c19cf57422a6affected · git
- 2039f26f3aca5b0e419b98f65dd36481337b86ee and later · before a71eb8f730a91271cf47ce291e785b6b7e54622faffected · git
- 2039f26f3aca5b0e419b98f65dd36481337b86ee and later · before ca119656baa8f48a56e0c2f3ab63fdd33ca9e307affected · git
- 2039f26f3aca5b0e419b98f65dd36481337b86ee and later · before 475405593de2b796224c6297aece44f321195919affected · git
- 2039f26f3aca5b0e419b98f65dd36481337b86ee and later · before f1471aa76d74e0df3b2a90731ca0208f498c670baffected · git
- 2039f26f3aca5b0e419b98f65dd36481337b86ee and later · before 68b41e68a62299f26cb16af422b5c7d1c69dafd9affected · git
- 2039f26f3aca5b0e419b98f65dd36481337b86ee and later · before db8f1dcf5950b91886b9df4270bc816370d292c1affected · git
- 2039f26f3aca5b0e419b98f65dd36481337b86ee and later · before d1d53aa30ab3b5ae89161c9cc840b3f7489ad386affected · git
- 5.10.56 and later · before 5.10.261affected · 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 | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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 | 4.20 | Vendor (CNA) |
| Linux Linux | 475405593de2b796224c6297aece44f321195919 | Vendor (CNA) |
| Linux Linux | 5.10.261 | Vendor (CNA) |
| Linux Linux | 5.14 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 68b41e68a62299f26cb16af422b5c7d1c69dafd9 | Vendor (CNA) |
| Linux Linux | a71eb8f730a91271cf47ce291e785b6b7e54622f | Vendor (CNA) |
| Linux Linux | ca119656baa8f48a56e0c2f3ab63fdd33ca9e307 | Vendor (CNA) |
| Linux Linux | d1d53aa30ab3b5ae89161c9cc840b3f7489ad386 | Vendor (CNA) |
| Linux Linux | db8f1dcf5950b91886b9df4270bc816370d292c1 | Vendor (CNA) |
| Linux Linux | e62268e695075a481a6c4feeb022c19cf57422a6 | Vendor (CNA) |
| Linux Linux | f1471aa76d74e0df3b2a90731ca0208f498c670b | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | 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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
Show all references (7 more)Show less
- git.kernel.org/stable/c/68b41e68a62299f26cb16af422b5c7d1c69dafd9
- git.kernel.org/stable/c/a71eb8f730a91271cf47ce291e785b6b7e54622f
- git.kernel.org/stable/c/ca119656baa8f48a56e0c2f3ab63fdd33ca9e307
- git.kernel.org/stable/c/d1d53aa30ab3b5ae89161c9cc840b3f7489ad386
- git.kernel.org/stable/c/db8f1dcf5950b91886b9df4270bc816370d292c1
- git.kernel.org/stable/c/e62268e695075a481a6c4feeb022c19cf57422a6
- git.kernel.org/stable/c/f1471aa76d74e0df3b2a90731ca0208f498c670b
Vendor advisories and official records. Exploit/PoC links are deliberately left out.