CVE-2026-52973
Last modified
CVE-2026-52973 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: futex: Drop CLONE_THREAD requirement for private default hash alloc Currently need_futex_hash_allocate_default() depends on strict pthread semantics, abusing CLONE_THREAD. This breaks the non-concurrency assumptions when doing the mm->futex_ref pcpu allocations, leading to bugs[0] when sharing the mm in other ways; ie: BUG: KASAN: slab-use-after-free in futex_hash_put ... EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: futex: Drop CLONE_THREAD requirement for private default hash alloc Currently need_futex_hash_allocate_default() depends on strict pthread semantics, abusing CLONE_THREAD. This breaks the non-concurrency assumptions when doing the mm->futex_ref pcpu allocations, leading to bugs[0] when sharing the mm in other ways; ie: BUG: KASAN: slab-use-after-free in futex_hash_put ... where the +1 bias can end up on a percpu counter that mm->futex_ref no longer points at. Loosen the check to cover any CLONE_VM clone, except vfork(). Excluding vfork keeps the existing paths untouched (no overhead), and we can't race in the first place: either the parent is suspended and the child runs alone, or mm->futex_ref is already allocated from an earlier CLONE_VM.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.17.1, < 6.18.33 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.10 | — |
| Linux | Linux Kernel | 6.17 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
- https://access.redhat.com/security/cve/CVE-2026-52973Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2492413Issue Tracking, Third Party Advisory
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-52973.jsonThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-52973?
How severe is CVE-2026-52973?
How do I fix CVE-2026-52973?
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-52968In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-52969In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-5297Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-52970In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52971In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-52972In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52974In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-52975In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-52976In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-52977In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52978In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-52979In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-52973?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
