CVE-2026-98037
Last modified
CVE-2026-98037 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: bpf: Reject untrusted allocated-object pointers When the final RCU read-side critical section ends, a local kptr is demoted to PTR_UNTRUSTED but retains MEM_ALLOC. The pointer may be NULL or may refer to an object whose lifetime is no longer protected. type_is_ptr_alloc_obj() nevertheless recognizes any PTR_TO_BTF_ID with MEM_ALLOC as a live allocated object.
Description
In the Linux kernel, the following vulnerability has been resolved: bpf: Reject untrusted allocated-object pointers When the final RCU read-side critical section ends, a local kptr is demoted to PTR_UNTRUSTED but retains MEM_ALLOC. The pointer may be NULL or may refer to an object whose lifetime is no longer protected. type_is_ptr_alloc_obj() nevertheless recognizes any PTR_TO_BTF_ID with MEM_ALLOC as a live allocated object. In particular, a refcount-only local kptr never carries NON_OWN_REF, so it still passes the bpf_refcount_acquire() argument check after RCU protection ends. The kfunc can then dereference NULL or stale memory. Make type_is_ptr_alloc_obj() reject PTR_UNTRUSTED pointers. Since type_is_non_owning_ref() is based on the same predicate, graph kfunc arguments obey the same live-object requirement. Fault-protected reads of the demoted pointer remain valid: writes are already rejected, and read fixups use bpf_may_fault_on_deref() rather than this predicate. [ kkd: Rewrote commit log ]
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 1b12171533a9bb23cf6fba7262b479028b65e1e8, < 092c2874dc1b2060fa77a465a971acd4fdf87683; >= 1b12171533a9bb23cf6fba7262b479028b65e1e8, < 135d542b97fa93e32c457d49d6e7b33ca7d05bae; >= 1b12171533a9bb23cf6fba7262b479028b65e1e8, < 6b1f786ad85a0b63393b76f5e634deab1a73198c; >= 1b12171533a9bb23cf6fba7262b479028b65e1e8, < 7441ee8276641bddaf1cba7bb75ef9c1458ceb3b |
| Linux | Linux | 6.8 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98037?
How severe is CVE-2026-98037?
How do I fix CVE-2026-98037?
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-98031In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98032In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98033In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98034In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98035In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98036In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98038In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98039In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9804A flaw was found in KubeVirt's virt-exportserver component. …7.7
- CVE-2026-98040In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98041In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-98042In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98037?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
