CVE-2026-72428bpf: Fix stack slot index in nospec checks
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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[].
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Aug 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 0e9280654aa482088ee6ef3deadef331f5ac5fb0 before e62268e695075a481a6c4feeb022c19cf57422a6; from 2039f26f3aca5b0e419b98f65dd36481337b86ee before a71eb8f730a91271cf47ce291e785b6b7e54622f; from 2039f26f3aca5b0e419b98f65dd36481337b86ee before ca119656baa8f48a56e0c2f3ab63fdd33ca9e307; from 2039f26f3aca5b0e419b98f65dd36481337b86ee before 475405593de2b796224c6297aece44f321195919; from 2039f26f3aca5b0e419b98f65dd36481337b86ee before f1471aa76d74e0df3b2a90731ca0208f498c670b; 2039f26f3aca5b0e419b98f65dd36481337b86ee builds before 68b41e68a62299f26cb16af422b5c7d1c69dafd9; from 2039f26f3aca5b0e419b98f65dd36481337b86ee before db8f1dcf5950b91886b9df4270bc816370d292c1; from 2039f26f3aca5b0e419b98f65dd36481337b86ee before d1d53aa30ab3b5ae89161c9cc840b3f7489ad386; and 7 more ranges | CNA record |
References
- https://git.kernel.org/stable/c/e62268e695075a481a6c4feeb022c19cf57422a6
- https://git.kernel.org/stable/c/a71eb8f730a91271cf47ce291e785b6b7e54622f
- https://git.kernel.org/stable/c/ca119656baa8f48a56e0c2f3ab63fdd33ca9e307
- https://git.kernel.org/stable/c/475405593de2b796224c6297aece44f321195919
- https://git.kernel.org/stable/c/f1471aa76d74e0df3b2a90731ca0208f498c670b
- https://git.kernel.org/stable/c/68b41e68a62299f26cb16af422b5c7d1c69dafd9
- https://git.kernel.org/stable/c/db8f1dcf5950b91886b9df4270bc816370d292c1
- https://git.kernel.org/stable/c/d1d53aa30ab3b5ae89161c9cc840b3f7489ad386
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.