# CVE-2026-98060: bpf: Reject resilient lock operations in rbtree callbacks

> A use-after-free vulnerability in the Linux kernel BPF subsystem allows local attackers to execute arbitrary code or escalate privileges via rbtree callbacks.

- **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:** BELL-CVE-2026-98060, DEBIAN-CVE-2026-98060, GHSA-5qvg-w7qr-xhvh, UBUNTU-CVE-2026-98060

## What is CVE-2026-98060?

CVE-2026-98060 is an use after free 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: Reject resilient lock operations in rbtree callbacks

__bpf_rbtree_add() keeps parent and link pointers live across calls to the
program-supplied comparison callback. The verifier therefore requires the
root's lock to remain held throughout the callback.

The helper path enforces this rule for bpf_spin_lock() and
bpf_spin_unlock(), but the resilient lock kfunc argument path does not.
Since resilient locks may protect BPF rbtree roots, a callback can release
the root lock and let another CPU remove and free the node referenced by
the in-progress tree walk. The walk then resumes using freed pointers.

Reject resilient lock kfuncs in an rbtree comparison callback, matching
the existing policy for the spin lock helpers. Resilient-lock-protected
trees remain valid when their comparison callbacks leave lock state alone.

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


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

Apply the vendor's patch.

## Is CVE-2026-98060 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98060 is an use after free 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-98060 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-98060/ (Markdown: https://insights.sbomify.com/CVE-2026-98060/index.md)
```

## Sources

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

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