CVE-2026-31554: futex: Require sys_futex_requeue() to have identical flags
Noroxi assessment
Priority: Monitor (action score 31/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.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 027145ace09fad4c7cbcd6c61fe9b429c63eb0e5, 18b7d09c2b794c71d4252f3ea2cf84ad12b73d6a, 19f94b39058681dec64a10ebeb6f23fe7fc3f77a.
Low priority for now. Upgrade to Linux Linux 027145ace09fad4c7cbcd6c61fe9b429c63eb0e5, 18b7d09c2b794c71d4252f3ea2cf84ad12b73d6a, 19f94b39058681dec64a10ebeb6f23fe7fc3f77a 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: Require sys_futex_requeue() to have identical flags Nicholas reported that his LLM found it was possible to create a UaF when sys_futex_requeue() is used with different flags. The initial motivation for allowing different flags was the variable sized futex, but since that hasn't been merged (yet), simply mandate the flags are identical, as is the case for the old style sys_futex() requeue operations.
- BDU:2026-12560
- ALSA-2026:51035
- RHSA-2026:51035
- SUSE-SU-2026:22276-1
- SUSE-SU-2026:22277-1
- SUSE-SU-2026:22278-1
- SUSE-SU-2026:22279-1
- SUSE-SU-2026:22280-1
- SUSE-SU-2026:22281-1
- SUSE-SU-2026:22282-1
- SUSE-SU-2026:22283-1
- SUSE-SU-2026:22288-1
- SUSE-SU-2026:22383-1
- SUSE-SU-2026:22384-1
- SUSE-SU-2026:22385-1
- SUSE-SU-2026:22386-1
- SUSE-SU-2026:22387-1
- SUSE-SU-2026:22388-1
- SUSE-SU-2026:22389-1
- SUSE-SU-2026:22390-1
- Published
- Apr 24, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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.7affected
- 0f4b5f972216782a4acb1ae00dcb55173847c2ff and later · before 027145ace09fad4c7cbcd6c61fe9b429c63eb0e5affected · git
- 0f4b5f972216782a4acb1ae00dcb55173847c2ff and later · before 18b7d09c2b794c71d4252f3ea2cf84ad12b73d6aaffected · git
- 0f4b5f972216782a4acb1ae00dcb55173847c2ff and later · before e2f78c7ec1655fedd945366151ba54fcb9580508affected · git
- 0f4b5f972216782a4acb1ae00dcb55173847c2ff and later · before 19f94b39058681dec64a10ebeb6f23fe7fc3f77aaffected · git
- before 6.7not affected · semver
- 6.12.80 and later · up to and including 6.12.*not affected · semver
- 6.18.21 and later · up to and including 6.18.*not affected · semver
- 6.19.11 and later · up to and including 6.19.*not affected · semver
- 7.0 and laternot affected · original_commit_for_fix
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.7.1 and later · before 6.12.80
- linux linux kernel6.13 and later · before 6.18.21
- linux linux kernel6.19 and later · before 6.19.11
- linux linux kernel6.7
- linux linux kernel7.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | kernel | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-core | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
| AlmaLinux:9 | kernel-debug-modules-core | before 5.14.0-687.36.1.el9_8 | 5.14.0-687.36.1.el9_8 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-31552Apr 24, 2026 · wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom30Monitor
- ← EarlierCVE-2026-31553Apr 24, 2026 · KVM: arm64: Fix the descriptor address in __kvm_at_swap_desc()35Monitor
- Later →CVE-2026-31555Apr 24, 2026 · futex: Clear stale exiting pointer in futex_lock_pi() retry path22Monitor
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 | 027145ace09fad4c7cbcd6c61fe9b429c63eb0e5 | Vendor (CNA) |
| Linux Linux | 18b7d09c2b794c71d4252f3ea2cf84ad12b73d6a | Vendor (CNA) |
| Linux Linux | 19f94b39058681dec64a10ebeb6f23fe7fc3f77a | Vendor (CNA) |
| Linux Linux | e2f78c7ec1655fedd945366151ba54fcb9580508 | Vendor (CNA) |
| almalinux:kernel | 5.14.0-687.36.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-687.36.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-687.36.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-687.36.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-687.36.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-687.36.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-687.36.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-687.36.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-687.36.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-687.36.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-687.36.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-687.36.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.12.85-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-687.36.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-687.36.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-687.36.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-687.36.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-687.36.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-687.36.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-687.36.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-687.36.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-687.36.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-687.36.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-687.36.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:5.14.0-687.36.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| suse:kernel-livepatch-SLE16_Update_0 | 14-160000.4.3 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
+11
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (2)
- SSVC exploitation— → none
- 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.