CVE-2026-80777: futex/pi: Plug private futex exec() race
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.20% (FIRST EPSS).
- Fixed version: Linux Linux 0478bc6bf197629fea0331d65b39eeea043c6cf0, c5f0bc9fd1cec4a00400cc727fcde03e0fde17cc, d7944cee62ec6cca1c90780a766960a57d3b4bb8.
Low priority for now. Upgrade to Linux Linux 0478bc6bf197629fea0331d65b39eeea043c6cf0, c5f0bc9fd1cec4a00400cc727fcde03e0fde17cc, d7944cee62ec6cca1c90780a766960a57d3b4bb8 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/pi: Plug private futex exec() race The check for private futexes whether the waiter's mm, which is stored in the futex_key and copied into the pi_state, is the same as the owner's mm is not sufficient for exec(). exec() has a gap where the mm check fails to give the correct answer: exec() ... exec_release_mm() futex_exec_release() tsk::futex::exit_state = EXITING; cleanup_robust_list(); 1) tsk::futex::exit_state = OK; ... old_mm = tsk::mm; 2) tsk::mm = ->mm; Between #1 and #2 the check for the mm is wrong as that mm is about to be swapped out and eventually freed. Plug this gap by: 1) Setting tsk::futex::exit_state to FUTEX_STATE_DEAD in futex_exec_release() 2) Setting tsk::futex::exit_state to FUTEX_STATE_OK after the mm has been switched. From a futex point of view the task is dead after it finished the robust list cleanup up to the point where it sets the state to OK again.
- Published
- Sep 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Is your version affected? Check itNoroxi 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
- 80367ad01d93ac781b0e1df246edaf006928002f and later · before fdf538b2e69653ff740e84042245018e5680cd7baffected · git
- 80367ad01d93ac781b0e1df246edaf006928002f and later · before 0478bc6bf197629fea0331d65b39eeea043c6cf0affected · git
- 80367ad01d93ac781b0e1df246edaf006928002f and later · before d7944cee62ec6cca1c90780a766960a57d3b4bb8affected · git
- 80367ad01d93ac781b0e1df246edaf006928002f and later · before c5f0bc9fd1cec4a00400cc727fcde03e0fde17ccaffected · 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-80774Sep 4, 2026 · HID: asus: fix missing hid_is_usb() check0Monitor
- ← EarlierCVE-2026-80775Sep 4, 2026 · futex: Fix race on the initial mm->futex.phash.ref allocation0Monitor
- Later →CVE-2026-80778Sep 4, 2026 · futex/pi: Reject cross-mm private futex owners0Monitor
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 | 0478bc6bf197629fea0331d65b39eeea043c6cf0 | Vendor (CNA) |
| Linux Linux | c5f0bc9fd1cec4a00400cc727fcde03e0fde17cc | Vendor (CNA) |
| Linux Linux | d7944cee62ec6cca1c90780a766960a57d3b4bb8 | Vendor (CNA) |
| Linux Linux | fdf538b2e69653ff740e84042245018e5680cd7b | 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).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 (1)
- 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.