# CVE-2026-92486: bpf: Fix CFI mismatch in task work callback

> A Control Flow Integrity mismatch in the Linux kernel BPF subsystem can cause a crash when task work callbacks are invoked.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-92486, DEBIAN-CVE-2026-92486, GHSA-vh7j-gj65-xh7c, UBUNTU-CVE-2026-92486

## What is CVE-2026-92486?

CVE-2026-92486 is a vulnerability in Linux, published on 17 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: Fix CFI mismatch in task work callback

BPF subprograms use the bpf_callback_t ABI, but task work invokes the
callback through a three-argument function pointer. This trips kCFI.

Store and invoke the callback as bpf_callback_t.

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


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

Apply the vendor's patch.

## Is CVE-2026-92486 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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