CVE-2026-64075
Last modified
CVE-2026-64075 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: fprobe: Fix unregister_fprobe() to wait for RCU grace period Commit 4346ba1604093 ("fprobe: Rewrite fprobe on function-graph tracer") changed fprobe to register struct fprobe to an rcu-hlist, but it forgot to wait for RCU GP. Thus there can be use-after-free if the fprobe is released right after unregistering. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: fprobe: Fix unregister_fprobe() to wait for RCU grace period Commit 4346ba1604093 ("fprobe: Rewrite fprobe on function-graph tracer") changed fprobe to register struct fprobe to an rcu-hlist, but it forgot to wait for RCU GP. Thus there can be use-after-free if the fprobe is released right after unregistering. This can be happened on fprobe event and sample module code. To fix this issue, add synchronize_rcu() in unregister_fprobe(). Note that BPF is OK because fprobe is used as a part of bpf_kprobe_multi_link. This unregisters its fprobe in bpf_kprobe_multi_link_release() and it is deallocated via bpf_kprobe_multi_link_dealloc(), which is invoked from bpf_link_defer_dealloc_rcu_gp() RCU callback. For BPF, this also introduced unregister_fprobe_async() which does NOT wait for RCU grace priod.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 4346ba1604093305a287e08eb465a9c15ba05b80, < 56b4cfcf1518245493c60fd39c56978f508f1816; >= 4346ba1604093305a287e08eb465a9c15ba05b80, < a4f6a9005ed6cfd360ef2520430927f05f92ffb0; >= 4346ba1604093305a287e08eb465a9c15ba05b80, < 657b594b2084b39a4bc6d8493aa2140cb00cea49 |
| Linux | Linux | 6.14 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-64075?
How severe is CVE-2026-64075?
How do I fix CVE-2026-64075?
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-64069In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64070In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64071In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64072In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64073In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64074In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64076In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64077In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64078In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64079In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6408Tanium addressed an information disclosure vulnerability in …2.7
- CVE-2026-64080In the Linux kernel, the following vulnerability has been re…9.3
Are you affected by CVE-2026-64075?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
