CVE-2026-72428 — bpf: Fix stack slot index in nospec checks
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[].
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 0e9280654aa482088ee6ef3deadef331f5ac5fb0 and < e62268e695075a481a6c4feeb022c19cf57422a6≥ 2039f26f3aca5b0e419b98f65dd36481337b86ee and < a71eb8f730a91271cf47ce291e785b6b7e54622f≥ 2039f26f3aca5b0e419b98f65dd36481337b86ee and < ca119656baa8f48a56e0c2f3ab63fdd33ca9e307≥ 2039f26f3aca5b0e419b98f65dd36481337b86ee and < 475405593de2b796224c6297aece44f321195919≥ 2039f26f3aca5b0e419b98f65dd36481337b86ee and < f1471aa76d74e0df3b2a90731ca0208f498c670b≥ 2039f26f3aca5b0e419b98f65dd36481337b86ee and < 68b41e68a62299f26cb16af422b5c7d1c69dafd9≥ 2039f26f3aca5b0e419b98f65dd36481337b86ee and < db8f1dcf5950b91886b9df4270bc816370d292c1≥ 2039f26f3aca5b0e419b98f65dd36481337b86ee and < d1d53aa30ab3b5ae89161c9cc840b3f7489ad386 and 8 moreversion 872968502114d68c21419cf7eb5ab97717e7b803version f5893af2704eb763eb982f01d573f5b19f06b623version 0b27bdf02c400684225ee5ee99970bcbf5082282≥ 5.10.56 and < 5.10.261≥ 4.19.207 and < 4.20≥ 5.4.146 and < 5.5≥ 5.13.8 and < 5.14version 5.14 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 29, 2026 · 14 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/a71eb8f730a91271cf47ce291e785b6b7e54622f
- git.kernel.org/stable/c/ca119656baa8f48a56e0c2f3ab63fdd33ca9e307
- git.kernel.org/stable/c/475405593de2b796224c6297aece44f321195919
- git.kernel.org/stable/c/db8f1dcf5950b91886b9df4270bc816370d292c1
- git.kernel.org/stable/c/d1d53aa30ab3b5ae89161c9cc840b3f7489ad386
- git.kernel.org/stable/c/68b41e68a62299f26cb16af422b5c7d1c69dafd9
- git.kernel.org/stable/c/e62268e695075a481a6c4feeb022c19cf57422a6
- git.kernel.org/stable/c/f1471aa76d74e0df3b2a90731ca0208f498c670b
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-72428 is "bpf: Fix stack slot index in nospec checks", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.