CVE-2026-31555futex: Clear stale exiting pointer in futex_lock_pi() retry path
- 5.5MediumCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: futex: Clear stale exiting pointer in futex_lock_pi() retry path Fuzzying/stressing futexes triggered: WARNING: kernel/futex/core.c:825 at wait_for_owner_exiting+0x7a/0x80, CPU#11: futex_lock_pi_s/524 When futex_lock_pi_atomic() sees the owner is exiting, it returns -EBUSY and stores a refcounted task pointer in 'exiting'. After wait_for_owner_exiting() consumes that reference, the local pointer is never reset to nil. Upon a retry, if futex_lock_pi_atomic() returns a different error, the bogus pointer is passed to wait_for_owner_exiting(). CPU0 CPU1 CPU2 futex_lock_pi(uaddr) // acquires the PI futex exit() futex_cleanup_begin() futex_state = EXITING; futex_lock_pi(uaddr) futex_lock_pi_atomic() attach_to_pi_owner() // observes EXITING *exiting = owner; // takes ref return -EBUSY wait_for_owner_exiting(-EBUSY, owner) put_task_struct(); // drops ref // exiting still points to owner goto retry; futex_lock_pi_atomic() lock_pi_update_atomic() cmpxchg(uaddr) *uaddr ^= WAITERS // whatever // value changed return -EAGAIN; wait_for_owner_exiting(-EAGAIN, exiting) // stale WARN_ON_ONCE(exiting) Fix this by resetting upon retry, essentially aligning it with requeue_pi.
Timeline
ID reserved
By Linux
- 46 days later
· 46 days later
Published
- 7 months later
· 7 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 3ef240eaff36b8119ac9e2ea17cbf41179c930ba – < 33095ae3bdde5e5c264d7e88a2f3e7703a26c7aa
- affected 3ef240eaff36b8119ac9e2ea17cbf41179c930ba – < e7824ec168d2ac883a213cd1f4d6cc0816002a85
- affected 3ef240eaff36b8119ac9e2ea17cbf41179c930ba – < 5e8e06bf8909e79b4acd950cf578cfc2f10bbefa
- affected 3ef240eaff36b8119ac9e2ea17cbf41179c930ba – < de7c0c04ad868f2cee6671b11c0a6d20421af1da
- affected 3ef240eaff36b8119ac9e2ea17cbf41179c930ba – < 7475dfad10a05a5bfadebf5f2499bd61b19ed293
- affected 3ef240eaff36b8119ac9e2ea17cbf41179c930ba – < 92e47ad03e03dbb5515bdf06444bf6b1e147310d
- affected 3ef240eaff36b8119ac9e2ea17cbf41179c930ba – < 71112e62807d1925dc3ae6188b11f8cfc85aec23
- affected 3ef240eaff36b8119ac9e2ea17cbf41179c930ba – < 210d36d892de5195e6766c45519dfb1e65f3eb83
- affected f2a9957e5c08b1b1caacd18a3dc4c0a1bdb7b463
- affected cf16e42709aa86aa3e37f3acc3d13d5715d90096
- affected 61fa9f167caaa73d0a7c88f498eceeb12c6fa3db
- affected 7874eee0130adf9bee28e8720bb5dd051089def3
- affected fc3b55ef2c840bb2746b2d8121a0788de84f7fac
- affected 4.4.255 – < 4.5
- affected 4.9.255 – < 4.10
- affected 4.14.158 – < 4.15
- affected 4.19.172 – < 4.20
- affected 5.4.1 – < 5.5
- affected 5.5
- unaffected < 5.5
- unaffected 5.10.253 – ≤ 5.10.*
- unaffected 5.15.203 – ≤ 5.15.*
- unaffected 6.1.168 – ≤ 6.1.*
- unaffected 6.6.131 – ≤ 6.6.*
- unaffected 6.12.80 – ≤ 6.12.*
- unaffected 6.18.21 – ≤ 6.18.*
- unaffected 6.19.11 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References11
- https://git.kernel.org/stable/c/33095ae3bdde5e5c264d7e88a2f3e7703a26c7aa (opens in a new tab)
- https://git.kernel.org/stable/c/e7824ec168d2ac883a213cd1f4d6cc0816002a85 (opens in a new tab)
- https://git.kernel.org/stable/c/5e8e06bf8909e79b4acd950cf578cfc2f10bbefa (opens in a new tab)
- https://git.kernel.org/stable/c/de7c0c04ad868f2cee6671b11c0a6d20421af1da (opens in a new tab)
- https://git.kernel.org/stable/c/7475dfad10a05a5bfadebf5f2499bd61b19ed293 (opens in a new tab)
- https://git.kernel.org/stable/c/92e47ad03e03dbb5515bdf06444bf6b1e147310d (opens in a new tab)
- https://git.kernel.org/stable/c/71112e62807d1925dc3ae6188b11f8cfc85aec23 (opens in a new tab)
- https://git.kernel.org/stable/c/210d36d892de5195e6766c45519dfb1e65f3eb83 (opens in a new tab)
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html (opens in a new tab)
- https://cert-portal.siemens.com/productcert/html/ssa-019113.html (opens in a new tab)
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-25448 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-31555)Record last updated .