CVE-2026-31554

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-24. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

April 24, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

futex: Require sys_futex_requeue() to have identical flags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e2f78c7ec1655fedd945366151ba54fcb9580508
generic

futex: Require sys_futex_requeue() to have identical flags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/19f94b39058681dec64a10ebeb6f23fe7fc3f77a
generic

futex: Require sys_futex_requeue() to have identical flags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18b7d09c2b794c71d4252f3ea2cf84ad12b73d6a
generic

futex: Require sys_futex_requeue() to have identical flags - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/027145ace09fad4c7cbcd6c61fe9b429c63eb0e5

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.80—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(13)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 240 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:52 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-04 03:16 UTCOSV refresh
  11. 2026-09-02 14:11 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 14:46 UTCEPSS rescore
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-24 14:17 UTCEPSS rescore
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 14:52 UTCEG score recompute
  3. 2026-08-17 14:52 UTCVendor advisory
  4. 2026-08-17 14:52 UTCGHSA enrichment
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 05:48 UTCEG score recompute
  8. 2026-08-16 05:48 UTCVendor advisory
  9. 2026-08-16 05:48 UTCGHSA enrichment
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 16:07 UTCVendor advisory
  13. 2026-08-14 16:07 UTCGHSA enrichment
  14. 2026-08-14 04:09 UTCEG score recompute
  15. 2026-08-14 04:09 UTCVendor advisory
  16. 2026-08-14 04:09 UTCGHSA enrichment
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 08:32 UTCVendor advisory
  19. 2026-08-13 08:32 UTCGHSA enrichment
  20. 2026-08-12 17:52 UTCEG score recompute
  21. 2026-08-12 17:52 UTCVendor advisory
  22. 2026-08-12 17:52 UTCGHSA enrichment
  23. 2026-08-12 13:50 UTCEPSS rescore
  24. 2026-08-11 16:42 UTCEG score recompute
  25. 2026-08-11 16:42 UTCVendor advisory
  26. 2026-08-11 16:42 UTCGHSA enrichment
  27. 2026-08-11 02:10 UTCEG score recompute
  28. 2026-08-11 02:10 UTCVendor advisory
  29. 2026-08-11 02:10 UTCGHSA enrichment
  30. 2026-08-11 00:00 UTCEPSS rescore
  31. 2026-08-10 03:18 UTCVendor advisory
  32. 2026-08-10 03:18 UTCGHSA enrichment
  33. 2026-08-09 15:19 UTCEG score recompute
  34. 2026-08-09 15:19 UTCVendor advisory
  35. 2026-08-09 15:19 UTCGHSA enrichment
  36. 2026-08-09 13:46 UTCEPSS rescore
  37. 2026-08-09 03:21 UTCEG score recompute
  38. 2026-08-09 03:21 UTCVendor advisory
  39. 2026-08-09 03:21 UTCGHSA enrichment
  40. 2026-08-08 16:37 UTCEPSS rescore
  41. 2026-08-08 12:35 UTCVendor advisory
  42. 2026-08-08 12:35 UTCGHSA enrichment
  43. 2026-08-08 00:35 UTCEG score recompute
  44. 2026-08-08 00:35 UTCVendor advisory
  45. 2026-08-08 00:35 UTCGHSA enrichment
  46. 2026-08-07 12:37 UTCEG score recompute
  47. 2026-08-07 12:37 UTCVendor advisory
  48. 2026-08-07 12:37 UTCGHSA enrichment
  49. 2026-08-06 13:46 UTCEPSS rescore
  50. 2026-08-06 12:36 UTCVendor advisory
  51. 2026-08-06 12:36 UTCGHSA enrichment
  52. 2026-08-06 00:37 UTCEG score recompute
  53. 2026-08-06 00:37 UTCVendor advisory
  54. 2026-08-06 00:37 UTCGHSA enrichment
  55. 2026-08-05 19:17 UTCEPSS rescore
  56. 2026-08-05 12:38 UTCEG score recompute
  57. 2026-08-05 12:38 UTCVendor advisory
  58. 2026-08-05 12:38 UTCGHSA enrichment
  59. 2026-08-04 15:10 UTCEPSS rescore
  60. 2026-08-04 10:38 UTCEPSS rescore
  61. 2026-08-03 21:06 UTCEG score recompute
  62. 2026-08-03 21:06 UTCVendor advisory
  63. 2026-08-03 21:06 UTCGHSA enrichment
  64. 2026-08-03 10:36 UTCEPSS rescore
  65. 2026-08-02 23:25 UTCVendor advisory
  66. 2026-08-02 23:25 UTCGHSA enrichment
  67. 2026-08-02 11:26 UTCEG score recompute
  68. 2026-08-02 11:26 UTCVendor advisory
  69. 2026-08-02 11:26 UTCGHSA enrichment
  70. 2026-08-02 02:27 UTCEPSS rescore
  71. 2026-08-01 04:16 UTCEPSS rescore
  72. 2026-07-30 16:27 UTCEPSS rescore
  73. 2026-07-30 01:30 UTCEPSS rescore
  74. 2026-07-28 15:36 UTCEPSS rescore
  75. 2026-07-26 14:54 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-31554?
CVE-2026-31554 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: futex: Require sysfutexrequeue() to have identical flags Nicholas reported that his LLM found it was possible to create a UaF when sysfutexrequeue() is used with different flags. The initial motivation for allowing different flags…
When was CVE-2026-31554 disclosed?
CVE-2026-31554 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31554 actively exploited?
CVE-2026-31554 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.1% of all scored CVEs.
What is the CVSS score of CVE-2026-31554?
CVE-2026-31554 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31554?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31554, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31554

Explore →

Is Your Infrastructure Affected by CVE-2026-31554?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs