bpf: Zero queue and stack outputs on lock failure (CVE-2026-92520) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-92520

bpf: Zero queue and stack outputs on lock failure

Answer in brief

CVE-2026-92520 records a Unknown severity vulnerability in bpf: Zero queue and stack outputs on lock failure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=a34a9f1a19afe9c60ca0ea61dfeee63a1c2baac8 <1534c4bff3aaca19c4c9a82f93e9b81f7c983de3 \|\| >=a34a9f1a19afe9c60ca0ea61dfeee63a1c2baac8 <e2396b8a562073787e627a5f483f1bc5c452fa6a \|\| >=a34a9f1a19afe9c60ca0ea61dfeee63a1c2baac8 <7ac6e1ae41a09f1dd4baeeff1d028ae49ee01232 \|\| 40e34ea01748e5b8afdd40a172868be1e1ab0ede \|\| 388c9d3eefaea99828ee5000c693128a5b41ee7c \|\| acabf5df49aa3a4f9c96200102d893351b511a88 \|\| e388671635acf470f0986d874389148fd234620b \|\| 232f0ba4d69263af5912e279fcc32fef2882b1dc \|\| >=5.4.258 <5.5 \|\| >=5.10.198 <5.11 \|\| >=5.15.134 <5.16 \|\| >=6.1.56 <6.2 \|\| >=6.5.6 <6.6	1534c4bff3aaca19c4c9a82f93e9b81f7c983de3, e2396b8a562073787e627a5f483f1bc5c452fa6a, 7ac6e1ae41a09f1dd4baeeff1d028ae49ee01232, 5.5, 5.11, 5.16, 6.2, 6.6
Linux/Linuxgeneric	6.6	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 1534c4bff3aaca19c4c9a82f93e9b81f7c983de3 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.