CVE-2026-72428

bpf: Fix stack slot index in nospec checks

N/A
Published: August 15, 2026 at 05:56 AM UTC
Updated: August 17, 2026 at 06:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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[].

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.19.207v ≥ 5.13.8v ≥ 5.4.1464.19.207 ≤ v < 4.205.10.56 ≤ v < 5.10.2615.13.8 ≤ v < 5.145.14 ≤ v < 5.15.2125.14 ≤ v < 6.1.1785.14 ≤ v < 6.12.975.14 ≤ v < 6.18.405.14 ≤ v < 6.6.1455.14 ≤ v < 7.1.55.14 ≤ v < 7.25.4.146 ≤ v < 5.50b27bdf02c400684225ee5ee99970bcbf50822820e9280654aa482088ee6ef3deadef331f5ac5fb02039f26f3aca5b0e419b98f65dd36481337b86ee4.19.2075.10.565.13.85.145.4.146872968502114d68c21419cf7eb5ab97717e7b803f5893af2704eb763eb982f01d573f5b19f06b623
Vendor states this is fixed in 475405593de2b796224c6297aece44f321195919 (fixed)
Vendor states this is fixed in 68b41e68a62299f26cb16af422b5c7d1c69dafd9 (fixed)
Vendor states this is fixed in a71eb8f730a91271cf47ce291e785b6b7e54622f (fixed)
Vendor states this is fixed in ca119656baa8f48a56e0c2f3ab63fdd33ca9e307 (fixed)
Vendor states this is fixed in d1d53aa30ab3b5ae89161c9cc840b3f7489ad386 (fixed)
Vendor states this is fixed in db8f1dcf5950b91886b9df4270bc816370d292c1 (fixed)
Vendor states this is fixed in e62268e695075a481a6c4feeb022c19cf57422a6 (fixed)
Vendor states this is fixed in f1471aa76d74e0df3b2a90731ca0208f498c670b (fixed)
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.14 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card