CVE-2026-31554·Kernel vulnerability
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.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.19.11
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.21% — higher than 11% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-31554 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.21%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 6.19.11
Fixed in: 6.19.11
How to fix this CVE
Update your Linux kernel to version 6.19.11 or later to resolve a use-after-free vulnerability in the futex requeue mechanism. This flaw could allow local users with sufficient privileges to trigger memory corruption by mismatching futex flags during requeue operations. Apply the kernel update and reboot your system to fully mitigate the issue.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check your kernel version: uname -r — ensure it is 6.19.11 or higher, or not in the 6.19.x range
- Verify futex syscall tracing is enabled: cat /proc/sys/kernel/ftrace_enabled — futex-related syscalls should be logged if tracing is active
- Search kernel logs for futex-related errors: sudo dmesg | grep -i futex — look for UaF or memory corruption warnings
- Confirm the patch was applied by checking kernel build info: cat /proc/version | grep 6.19 — verify the version string reflects 6.19.11 or later
FAQ
What is CVE-2026-31554?
CVE-2026-31554 is a use-after-free vulnerability in the Linux kernel's futex requeue system that occurs when mismatched flags are passed to sys_futex_requeue(). This allows local attackers with user-level privileges to corrupt kernel memory and potentially escalate privileges.
Is CVE-2026-31554 being actively exploited?
No, CVE-2026-31554 is not listed on the CISA KEV catalog and no public exploits are currently available. However, the vulnerability was discovered through automated LLM security analysis, indicating a non-trivial attack path.
What versions of Kernel are affected by CVE-2026-31554?
Linux kernel versions 6.19 through 6.19.11 are affected. The vulnerability was patched in kernel 6.19.11 and later stable releases.
How do I check if my server is vulnerable to CVE-2026-31554?
Run 'uname -r' and compare the output against the affected range 6.19.0–6.19.10. If your kernel falls within this range, your system is vulnerable and requires immediate patching.
Does Defensia detect CVE-2026-31554?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-31554 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-31554. Free for 1 server.
Get started free