# CVE-2026-80675: libbpf: Reject non-exclusive metadata maps in the signed loader

> A flaw in the Linux kernel's signed BPF loader allows bypassing integrity checks if map exclusivity is not enforced, potentially allowing stale data validation.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 29 Aug 2026
- **Also known as:** BELL-CVE-2026-80675, DEBIAN-CVE-2026-80675, GHSA-82gv-94cv-gr24, UBUNTU-CVE-2026-80675

## What is CVE-2026-80675?

CVE-2026-80675 is a high-severity vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-80675?


## How do I fix CVE-2026-80675?

Apply the vendor's patch.

## Is CVE-2026-80675 being exploited?

There is no known exploitation of CVE-2026-80675 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80675 and fix it if it is affected.

What it is: CVE-2026-80675 is a high-severity vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80675 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80675/ (Markdown: https://insights.sbomify.com/CVE-2026-80675/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80675
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80675
- OSV: https://osv.dev/vulnerability/CVE-2026-80675

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80675/
Summaries are generated and may contain mistakes; the official description above is the record.