CVE-2026-31555: futex: Clear stale exiting pointer in futex_lock_pi() retry path
Published Apr 24, 2026
·Updated
futex: Clear stale exiting pointer in futexlockpi() retry path
Affected Software
22 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=4.4.255<4.5
Linux Linux kernel>=4.9.255<4.10
Linux Linux kernel>=4.14.158<4.15
Linux Linux kernel>=4.19.172<4.20
Linux Linux kernel>=5.4.1<5.5
Linux Linux kernel>=5.5.1<5.10.253
Linux Linux kernel>=5.11<5.15.203
Linux Linux kernel>=5.16<6.1.168
Linux Linux kernel>=6.2<6.6.131
Linux Linux kernel>=6.7<6.12.80
Linux Linux kernel>=6.13<6.18.21
Linux Linux kernel>=6.19<6.19.11
Linux Linux kernel=5.5
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
Linux Linux kernel=7.0-rc6
Linux Linux kernel=7.0-rc7
Microsoft azl3 kernel 6.6.130.1-3
Event History
Apr 24, 2026
CVE Published
via MITRE·02:35 PM
Data Sourced
via MITRE·02:35 PM
Description
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityAffected Software
Apr 26, 2026
Data Sourced
via Microsoft·08:01 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:01 AM
Affected Software
Updated
via Microsoft·08:01 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2026-31555?
CVE-2026-31555 has been rated as a high-severity vulnerability due to its potential impact on Linux kernel stability.
2
How do I fix CVE-2026-31555?
To remediate CVE-2026-31555, upgrade your Linux kernel to the latest stable version that addresses this issue.
3
What are the affected versions of Linux for CVE-2026-31555?
CVE-2026-31555 affects multiple Linux kernel versions, specifically those between 4.4.255 and 6.19.
4
What types of systems are impacted by CVE-2026-31555?
CVE-2026-31555 impacts any system running vulnerable versions of the Linux kernel.
5
Has CVE-2026-31555 been actively exploited in the wild?
As of now, there are no confirmed reports of active exploitation of CVE-2026-31555 in the wild.