# CVE-2026-98046: bpf: Mark bpf_btf_find_by_name_kind() as sleepable

> A local attacker can trigger a kernel crash by calling a BPF helper in a non-sleepable context, causing a denial of service.

- **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:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-104603, BELL-CVE-2026-98046, DEBIAN-CVE-2026-98046, GHSA-mcxj-647x-qcfv, UBUNTU-CVE-2026-98046

## What is CVE-2026-98046?

CVE-2026-98046 is a denial of service vulnerability in Linux, published on 25 Sep 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: Mark bpf_btf_find_by_name_kind() as sleepable

When bpf_btf_find_by_name_kind() finds a type in module BTF, it
returns a new BTF object fd through __btf_new_fd(). This reaches
anon_inode_getfd(), which can sleep while allocating or expanding the
current task fd table.

The helper prototype does not set might_sleep, so the verifier allows
the helper in non-sleepable contexts such as BPF timer callbacks. The
fd allocation can then sleep in softirq context and install the fd into
the interrupted task.

Mark the helper as sleepable. This preserves calls from the main body
of a sleepable syscall program while rejecting calls from its
non-sleepable regions.

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


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

Apply the vendor's patch.

## Is CVE-2026-98046 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98046 is a denial of service vulnerability in Linux, published on 25 Sep 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-98046 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-98046/ (Markdown: https://insights.sbomify.com/CVE-2026-98046/index.md)
```

## Sources

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

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