# CVE-2026-74360: bpf: Reject exclusive maps for bpf_map_elem iterators

> Local attackers can bypass BPF map exclusivity checks via iterators to modify exclusive map values, potentially leading to privilege escalation.

- **Severity:** Not scored
- **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:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-74360, DEBIAN-CVE-2026-74360, GHSA-qj57-hhqm-6w8v, UBUNTU-CVE-2026-74360

## What is CVE-2026-74360?

CVE-2026-74360 is a missing authorization vulnerability in Linux, published on 15 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:

bpf: Reject exclusive maps for bpf_map_elem iterators

Exclusive maps (aka excl_prog_hash) are meant to be reachable only
from the single program whose hash matches. This is enforced by
check_map_prog_compatibility() when the map is referenced from a
program such as signed BPF loaders.

A bpf_map_elem iterator, however, binds its target map at attach
time in bpf_iter_attach_map() instead of referencing it from the
program, so the exclusivity check is never reached. On top of that,
the iterator exposes the map value as a writable buffer.

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


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

Apply the vendor's patch.

## Is CVE-2026-74360 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74360 is a missing authorization vulnerability in Linux, published on 15 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-74360 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-74360/ (Markdown: https://insights.sbomify.com/CVE-2026-74360/index.md)
```

## Sources

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

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