libbpf: Reject non-exclusive metadata maps in the signed loader (CVE-2026-80675) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80675

libbpf: Reject non-exclusive metadata maps in the signed loader

Answer in brief

CVE-2026-80675 records a Unknown severity vulnerability in libbpf: Reject non-exclusive metadata maps in the signed loader. 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 Aug 28, 2026Updated Aug 28, 2026Source checked Aug 28, 2026First seen by HOL Aug 28, 2026Material review Aug 28, 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	>=fb2b0e290147ba01a53dfd92cf91058c9d2ee254 <b6862b6a25c6a925fb0b0e549ee4a52a8d2966fb \|\| >=fb2b0e290147ba01a53dfd92cf91058c9d2ee254 <0dad5adeb34b6f78a883e8faa6a1c947a240e7c9 \|\| >=fb2b0e290147ba01a53dfd92cf91058c9d2ee254 <0fb6c9ed6493b4af01be8bb0a384574eba7df636	b6862b6a25c6a925fb0b0e549ee4a52a8d2966fb, 0dad5adeb34b6f78a883e8faa6a1c947a240e7c9, 0fb6c9ed6493b4af01be8bb0a384574eba7df636
Linux/Linuxgeneric	6.18	Not reported

Recommended response

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

Evidence timeline and material changes

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

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: libbpf: Reject non-exclusive metadata maps in the signed loader The loader verifies map->sha against the metadata hash in its instructions. map->sha is calculated when BPF_OBJ_GET_INFO_BY_FD is called on the frozen map. While the map is frozen, the /signed loader/ must also ensure the map is exclusive, as, without exclusivity (which a hostile host could just omit when loading the loader), another BPF program with map access can mutate the contents afterwards, so the check passes on stale data. With the extra check as part of the signed loader, it now refuses to move on with map->sha validation if the host set it up wrongly.

Quoted source text, attributed separately from HOL analysis.