CVE-2026-98788
Last modified
CVE-2026-98788 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: futex: Fix private hash use-after-free on resize poll_state_synchronize_rcu(mm->futex.phash.batches) is used by futex_ref_drop() to check that a grace period has passed since the current hash was published. This relies on batches referencing a grace period which started after the hash pointer was assigned. __futex_pivot_hash() sets mmph->batches before it replaces mmph->hash: scoped_guard(rcu) { mmph->batches = get_state_synchronize_rcu(); rcu_assign_pointer(mmph->hash, new); } The scoped_guard(rcu) doesn't stop new grace periods from starting, and if one starts between those two assignments, futex_ref_drop() can move forward while a reader still holds a pointer to the old hash. Fix things by setting mmph->batches after assigning mmph->hash.
Description
In the Linux kernel, the following vulnerability has been resolved: futex: Fix private hash use-after-free on resize poll_state_synchronize_rcu(mm->futex.phash.batches) is used by futex_ref_drop() to check that a grace period has passed since the current hash was published. This relies on batches referencing a grace period which started after the hash pointer was assigned. __futex_pivot_hash() sets mmph->batches before it replaces mmph->hash: scoped_guard(rcu) { mmph->batches = get_state_synchronize_rcu(); rcu_assign_pointer(mmph->hash, new); } The scoped_guard(rcu) doesn't stop new grace periods from starting, and if one starts between those two assignments, futex_ref_drop() can move forward while a reader still holds a pointer to the old hash. Fix things by setting mmph->batches after assigning mmph->hash. The scoped_guard(rcu) isn't needed, so let's drop that as well.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 56180dd20c19e5b0fa34822997a9ac66b517e7b3, < 5d5dc18b3a9ac011619b7d3af4514bf9e9b6a6af; >= 56180dd20c19e5b0fa34822997a9ac66b517e7b3, < f35e3b5784221654f9cdbd6222275a7fa203f6c3 |
| Linux | Linux | 6.17 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98788?
How severe is CVE-2026-98788?
How do I fix CVE-2026-98788?
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-98782In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98783In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98784In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98785In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98786In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98787In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98789In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9879Out of bounds write in ANGLE in Google Chrome prior to 148.0…8.8
- CVE-2026-98790In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98791In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98792In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98793In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98788?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
