Skip to main content
Mallory
HighVulnerability

CVE-2026-31554: Linux kernel futex requeue use-after-free with mismatched flags

Published Apr 24, 2026 · Updated 26 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.21%11th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Linux
IdentifiersCVE-2026-31554CWE-416 · Use After Free

CVE-2026-31554 is a use-after-free vulnerability in the Linux kernel's futex requeue implementation. Calling sys_futex_requeue() with different flags can trigger the invalid memory access. Support for differing flags was intended for variable-sized futex functionality that had not yet been merged. The fix requires identical flags, matching the behavior of legacy sys_futex() requeue operations. The vulnerability is locally reachable and can potentially compromise system confidentiality, integrity, and availability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause kernel memory corruption and potentially compromise confidentiality, integrity, and availability, including service disruption and possible local privilege escalation. The assigned CVSS v3.1 score is 7.8, with high impacts across all three categories. Practical exploitability and integrity impact remain uncertain; no known exploits are identified in the available vulnerability assessments.

Mitigation

If you can’t patch tonight, do this now.

No specific configuration-level mitigation is established because futexes are core kernel functionality. Until patched kernels can be deployed, restrict execution of untrusted local code and containers or tenant workloads that could make arbitrary futex system calls, and reduce local access by low-privileged users where operationally feasible.

Remediation

Patch, then assume compromise.

Install a vendor-supported kernel update containing the fix that enforces identical flags for sys_futex_requeue(). Fixed upstream releases include 6.12.80, 6.18.21, 6.19.11, and 7.0 in their respective branches. Applicable SUSE 16.0, SUSE Linux Micro 6.2, and openSUSE Leap 16.0 kernel packages have fixes at version 6.12.0-160000.33.1 or later. For affected Google Container-Optimized OS kernel packages, the identified fixed package versions are 19216.220.185 or later for COS 125 and 19506.120.52 or later for COS 129. Follow the applicable distribution advisory because affected status and backported fixes vary by product. Reboot into the updated kernel.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system
FAQ

Frequently asked questions

Is CVE-2026-31554 exploited in the wild?
As of Oct 24, 2026, Mallory has no reports of CVE-2026-31554 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-31554?
As of Oct 24, 2026, Mallory has found no public exploit for CVE-2026-31554.
Is there a patch for CVE-2026-31554?
Install a vendor-supported kernel update containing the fix that enforces identical flags for sys_futex_requeue(). Fixed upstream releases include 6.12.80, 6.18.21, 6.19.11, and 7.0 in their respective branches.
What products are affected by CVE-2026-31554?
Linux Kernel.
How severe is CVE-2026-31554?
CVE-2026-31554 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.21% (11th percentile) as of Oct 24, 2026.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.