CVE-2026-64259

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
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:

fuse-uring: make a fuse_req on SQE commit only findable after memcpy

Bad userspace might try to trick us and send commit SQEs request unique / commit-id of requests that are not even send to fuse-server (io_uring_cmd_done() not called) yet.

fuse_uring_commit_fetch() ends the fuse request when the ring entry has a wrong state, but that could have caused a use-after-free with the memcpy operations in fuse_uring_send_in_task(). In order to avoid such races the call of fuse_uring_add_to_pq() is moved after the copy operations and just before completing the io-uring request - malicious userspace cannot find the request anymore until all prepration work in fuse-client/kernel is completed.

This also moves fuse_uring_add_to_pq() a bit up in the code to avoid a forward declaration. Also not with a preparation commit, to make it easier to back port to older kernels.

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
5%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

fuse-uring: make a fuse_req on SQE commit only findable after memcpy - kernel/git/stable/linux.git - Linux kernel stable tree

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

fuse-uring: make a fuse_req on SQE commit only findable after memcpy - kernel/git/stable/linux.git - Linux kernel stable tree

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

fuse-uring: make a fuse_req on SQE commit only findable after memcpy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1efd3d474fc0ba74dfd984249bca78807d739812

Vendor Advisories for CVE-2026-64259(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 112× 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 143 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-64259?
CVE-2026-64259 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: fuse-uring: make a fuse_req on SQE commit only findable after memcpy Bad userspace might try to trick us and send commit SQEs request unique / commit-id of requests that are not even send to fuse-server (iouringcmd_done() not…
When was CVE-2026-64259 disclosed?
CVE-2026-64259 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64259 actively exploited?
CVE-2026-64259 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 94.8% of all scored CVEs.
What is the CVSS score of CVE-2026-64259?
CVE-2026-64259 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64259?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64259, 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-64259

Explore →

Is Your Infrastructure Affected by CVE-2026-64259?

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

Start Free Scan →Browse All CVEs