CVE-2026-64260

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: Avoid queue->stopped races and set/read that value under lock

There are several readers of queue->stopped that check the value under lock, but fuse_uring_commit_fetch() did not and actually the value was not set under the lock in fuse_uring_abort_end_requests() either. Especially in fuse_uring_commit_fetch it is important to check under a lock, because due to races 'struct fuse_req' might be freed with fuse_request_end, but another thread/cpu might already do teardown work.

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
2%
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: Avoid queue->stopped races and set/read that value under lock - kernel/git/stable/linux.git - Linux kernel stable tree

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

fuse-uring: Avoid queue->stopped races and set/read that value under lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4021a3a79eee551d95fe1e1e7c1b195d34ba8c08
generic

fuse-uring: Avoid queue->stopped races and set/read that value under lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/39c8e925b207afceffaa5382416ed405e0223a03

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-64260?
CVE-2026-64260 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: fuse-uring: Avoid queue->stopped races and set/read that value under lock There are several readers of queue->stopped that check the value under lock, but fuseuringcommit_fetch() did not and actually the value was not set under the…
When was CVE-2026-64260 disclosed?
CVE-2026-64260 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-64260 actively exploited?
CVE-2026-64260 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 97.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64260?
CVE-2026-64260 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64260?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64260, 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-64260

Explore →

Is Your Infrastructure Affected by CVE-2026-64260?

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

Start Free Scan →Browse All CVEs