CVE-2025-39698

HIGHNVD 5.58.8▲
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2025-09-05. NVD baseline CVSS 5.5; sources differ by 3.3.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

io_uring/futex: ensure io_futex_wait() cleans up properly on failure

The io_futex_data is allocated upfront and assigned to the io_kiocb async_data field, but the request isn't marked with REQ_F_ASYNC_DATA at that point. Those two should always go together, as the flag tells io_uring whether the field is valid or not.

Additionally, on failure cleanup, the futex handler frees the data but does not clear ->async_data. Clear the data and the flag in the error path as well.

Thanks to Trend Micro Zero Day Initiative and particularly ReDress for reporting this.

CVSS v3
5.5
EG Score
8.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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

September 5, 2025

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

ZDI-25-915 - TrendAI™ Zero Day Initiative™ (ZDI)

https://www.zerodayinitiative.com/advisories/ZDI-25-915/
generic

io_uring/futex: ensure io_futex_wait() cleans up properly on failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

io_uring/futex: ensure io_futex_wait() cleans up properly on failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

io_uring/futex: ensure io_futex_wait() cleans up properly on failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/508c1314b342b78591f51c4b5dadee31a88335df

Vendor Advisories for CVE-2025-39698(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-94.96) @ noble2026-05-29ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1046.49+fips1) @ noble2026-05-29ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1045.48.1) @ noble2026-05-29ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1022.23) @ noble2026-05-29ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1043.43) @ noble2026-05-29ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1040.41) @ noble2026-05-29ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-05-29ubuntu
ubuntuoracle (6.8.0-1005) @ noble2026-05-29ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-05-29ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-29ubuntu
redhatkernel-0:6.12.0-55.37.1.el10_02025-09-29redhat
redhatkernel-0:5.14.0-570.49.1.el9_62025-09-29redhat
linuxKernel @ 6.12.44—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.41-1, 6.12.43-1, 6.12.43-1~bpo12+16.12.48-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (63 versions)6.16.5-1—

Weakness Classification(2)

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

Additional Vendor Advisories

(10)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 26× 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 142 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-39698?
CVE-2025-39698 is a high vulnerability published on September 5, 2025. In the Linux kernel, the following vulnerability has been resolved: iouring/futex: ensure iofutex_wait() cleans up properly on failure The iofutexdata is allocated upfront and assigned to the io_kiocb asyncdata field, but the request isn't marked with REQFASYNCDATA at that point. Those two should…
When was CVE-2025-39698 disclosed?
CVE-2025-39698 was first published in the National Vulnerability Database on September 5, 2025, 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-2025-39698 actively exploited?
CVE-2025-39698 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 90.9% of all scored CVEs.
What is the CVSS score of CVE-2025-39698?
CVE-2025-39698 has a CVSS v3 base score of 5.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.8.
How do I remediate CVE-2025-39698?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-39698, 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-2025-39698

Explore →

Is Your Infrastructure Affected by CVE-2025-39698?

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

Start Free Scan →Browse All CVEs