CVE-2026-98788: Linux kernel · futex: Fix private hash use-after-free on resize
Source GCVE Database
Not known to be exploited : upgrade to f35e3b5784221654f9cdbd6222275a7fa203f6c3 or 5d5dc18b3a9ac011619b7d3af4514bf9e9b6a6af soon.
Data as of 26 Oct 2026, 14:05 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f35e3b5784221654f9cdbd6222275a7fa203f6c3, 5d5dc18b3a9ac011619b7d3af4514bf9e9b6a6af
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to f35e3b5784221654f9cdbd6222275a7fa203f6c3 or 5d5dc18b3a9ac011619b7d3af4514bf9e9b6a6af.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel to reorder the assignment operations in the futex private hash resizing code, eliminating the use-after-free condition. Users should apply the official kernel update containing this fix when it becomes available. No additional mitigations are indicated by the vendor advisory.
Description
A use-after-free vulnerability in the Linux kernel's futex private hash resizing logic has been resolved. The issue arises because the order of assignments in the futex pivot hash function allows a grace period to start between setting batches and updating the hash pointer, potentially causing a reader to access freed memory. The fix involves reordering these assignments to prevent this race condition and removing an unnecessary scoped guard.