CVE-2026-92520

bpf: Zero queue and stack outputs on lock failure

Published Sep 17, 2026 CVSS n/a EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

bpf: Zero queue and stack outputs on lock failure

Queue and stack pop/peek helpers accept an uninitialized output buffer
because the verifier expects the helper to initialize it. The empty-map
error path clears the buffer, but a failed lock acquisition returns
-EBUSY without writing it.

Clear the output before returning -EBUSY so BPF programs cannot observe
uninitialized stack contents after a failed helper call.

Analysis

AI-generated

Technical impact

The Linux kernel contains BPF queue and stack helper functions that rely on the verifier to initialize output buffers. When a lock acquisition fails, the helper returns -EBUSY without writing into the buffer, exposing uninitialized stack contents to BPF programs. An attacker could read this uninitialized memory, causing kernel or user‑space information leakage.

Affected Systems

All Linux kernel versions that expose the uninitialized queue and stack helpers and have not yet applied the patch are potentially affected; the specific versions are not enumerated in the available data.

Risk and Exploitability

The EPSS score of < 1% indicates a very low likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog, and no CVSS score is available. Based on the description, an attacker requires the capacity to load or influence eBPF programs, implying a local or higher privilege context. Although the probability of exploitation appears low, the potential for kernel memory exposure warrants prompt remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Install the latest Linux kernel that includes the fix for the BPF helper uninitialized buffer issue. If a newer kernel is unavailable, check vendor channels for security errata and apply accordingly.
  • Where a kernel update is not immediately possible, minimize exposure by disabling or restricting eBPF execution for non‑privileged users via sysctl settings such as setting net.core.bpf_jit_enable=0 or restricting the BPF attachable objects with seccomp filters.
  • Verify that your system or applications do not load untrusted BPF bytecode; enforce input validation on BPF programs or audit them for proper usage.

Generated by OpenCVE AI on September 19, 2026 at 12:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4904-1 linux-6.12 security update
Debian DLA Debian DLA DLA-4906-1 linux security update
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-200
CWE-788
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: bpf: Zero queue and stack outputs on lock failure Queue and stack pop/peek helpers accept an uninitialized output buffer because the verifier expects the helper to initialize it. The empty-map error path clears the buffer, but a failed lock acquisition returns -EBUSY without writing it. Clear the output before returning -EBUSY so BPF programs cannot observe uninitialized stack contents after a failed helper call.
Title bpf: Zero queue and stack outputs on lock failure
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-788

    Access of Memory Location After End of Buffer

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 30, 2026, 12:35 PM
Reserved
Sep 16, 2026, 12:21 PM
Status
Received
Published
Sep 17, 2026, 5:17 PM
Modified
Oct 30, 2026, 1:20 PM