CVE-2026-80758: futex: Avoid private hash use-after-free on final put
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 12cd315a7b6a7d7db3f69d98bfe3909275e9451d, 1c7efabfbaf796f11000a46094a69955a01ec6cc, 25408c62ed4ebcd491d0e9e4b4a5b512547512e4.
Low priority for now. Upgrade to Linux Linux 12cd315a7b6a7d7db3f69d98bfe3909275e9451d, 1c7efabfbaf796f11000a46094a69955a01ec6cc, 25408c62ed4ebcd491d0e9e4b4a5b512547512e4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: futex: Avoid private hash use-after-free on final put futex_private_hash_put() drops the reference to fph before evaluating fph->mm for wake_up_var(). futex_ref_put() enables preemption again before returning. If that put drops the final reference and the task is preempted, another task can pivot to the replacement hash and free the old hash after an RCU grace period. The first task then reads fph->mm from the freed allocation when it resumes. KASAN reports a slab-use-after-free in futex_private_hash_put(), with the read at offset 24 in a freed kmalloc-512 allocation. The allocation and free stacks point to futex_hash_allocate() and the RCU free path, respectively. Load the mm pointer while the fph reference is still held and pass the saved value to wake_up_var(). wake_up_var() uses the pointer as a waitqueue key and does not dereference the mm through it.
- Published
- Sep 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.16affected
- bd54df5ea7cadac520e346d5f0fe5d58e635b6ba and later · before dba60d26e9dda3e157ad6b0934d4232f6c6904eeaffected · git
- bd54df5ea7cadac520e346d5f0fe5d58e635b6ba and later · before 12cd315a7b6a7d7db3f69d98bfe3909275e9451daffected · git
- bd54df5ea7cadac520e346d5f0fe5d58e635b6ba and later · before 25408c62ed4ebcd491d0e9e4b4a5b512547512e4affected · git
- bd54df5ea7cadac520e346d5f0fe5d58e635b6ba and later · before 1c7efabfbaf796f11000a46094a69955a01ec6ccaffected · git
- before 6.16not affected · semver
- 6.18.47 and later · up to and including 6.18.*not affected · semver
- 7.1.11 and later · up to and including 7.1.*not affected · semver
- 7.2.1 and later · up to and including 7.2.*not affected · semver
- 7.3 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | linux | before 7.1.12-1 | 7.1.12-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.2.5-1.1 | 7.2.5-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80912Sep 4, 2026 · selinux: reject an unclaimed class value in security_get_classes()0Monitor
- ← EarlierCVE-2026-80913Sep 4, 2026 · selinux: require every boolean value to be defined0Monitor
- Later →CVE-2026-80759Sep 4, 2026 · Bluetooth: hci_aml: validate firmware segment lengths0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 12cd315a7b6a7d7db3f69d98bfe3909275e9451d | Vendor (CNA) |
| Linux Linux | 1c7efabfbaf796f11000a46094a69955a01ec6cc | Vendor (CNA) |
| Linux Linux | 25408c62ed4ebcd491d0e9e4b4a5b512547512e4 | Vendor (CNA) |
| Linux Linux | dba60d26e9dda3e157ad6b0934d4232f6c6904ee | Vendor (CNA) |
| debian:linux | 7.1.12-1 · Debian:14 | Package registry (OSV) |
| opensuse:kernel-source | 7.2.5-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.