CVE-2026-98060
Last modified
CVE-2026-98060 is a vulnerability of currently unknown severity. 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.
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 0de2046137f976e7302d43ac01d9894d07ac1fff, < cc2e065ed206aecd9b94564779244f3ffb26e356; >= 0de2046137f976e7302d43ac01d9894d07ac1fff, < 71930202a0a0c49f0a3b45b41907a074cb780266; >= 0de2046137f976e7302d43ac01d9894d07ac1fff, < 7b7b8b5960102566bd625ae829d1f330c5b5d104 |
| Linux | Linux | 6.15 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98060?
How severe is CVE-2026-98060?
How do I fix CVE-2026-98060?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98055In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98056In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-98057In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98058In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98059In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9806A stored cross-site scripting (XSS) vulnerability exists in …6.3
- CVE-2026-98061In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98062In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98063In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98064In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98065In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98066In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98060?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
