CVE-2026-92520: bpf: Zero queue and stack outputs on lock failure
bpf: Zero queue and stack outputs on lock failure
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.114 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.52 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.6 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.6-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.12-1Fixed in 7.2.14-1
Event History
Frequently Asked Questions
Which BPF programs are exposed to this issue?
BPF programs that use queue or stack pop/peek helpers are exposed when a helper call fails to acquire its lock. The affected path returns -EBUSY without initializing the helper's output buffer.
What must happen for uninitialized data to be observable?
A queue or stack pop/peek helper must encounter a failed lock acquisition. In that case, the BPF program can observe uninitialized stack contents through the output buffer after the helper returns -EBUSY.
Does an empty queue or stack trigger the same behavior?
No. The empty-map error path already clears the output buffer; the issue is specific to the failed lock-acquisition path.