# CVE-2026-80607: tracing/probes: Remove WARN_ON_ONCE from parse_btf_arg

> A local attacker can trigger a kernel warning and potential denial of service by adding a kprobe event with a raw address and BTF parameter.

- **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:** 28 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-98048, BELL-CVE-2026-80607, DEBIAN-CVE-2026-80607, GHSA-x9r4-5m29-32qp, UBUNTU-CVE-2026-80607

## What is CVE-2026-80607?

CVE-2026-80607 is a denial of service 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:

tracing/probes: Remove WARN_ON_ONCE from parse_btf_arg

Sashiko found that user can cause this WARN_ON_ONCE() easily
with adding a kprobe event based on a raw address with BTF
parameter.

Since this is not an unexpected condition, remove the
WARN_ON_ONCE().

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


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

Apply the vendor's patch.

## Is CVE-2026-80607 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80607 is a denial of service 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-80607 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-80607/ (Markdown: https://insights.sbomify.com/CVE-2026-80607/index.md)
```

## Sources

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

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