CVE-2026-64264

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-25. NVD baseline CVSS 5.5; sources differ by 0.0.

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

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: fix EFAULT clobber in fuse_uring_commit

copy_from_user() returns the number of bytes not copied as an unsigned residual on failure (1..sizeof(struct fuse_out_header)). fuse_uring_commit stores that residual in ssize_t err, sets req->out.h.error to -EFAULT, then jumps to out: with err still holding the positive residual.

err = copy_from_user(&req->out.h, &ent->headers->in_out, sizeof(req->out.h)); if (err) { req->out.h.error = -EFAULT; goto out; /* err is the positive residual */ } ... out: fuse_uring_req_end(ent, req, err);

fuse_uring_req_end() then runs

if (error) req->out.h.error = error;

which overwrites the just-assigned -EFAULT with the positive residual. FUSE callers such as fuse_simple_request() test err < 0 to detect failure, so the positive value is interpreted as success and the caller proceeds with an uninitialised or partial req->out.args.

Fix by assigning err = -EFAULT in the failure branch before jumping to out, so fuse_uring_req_end() receives a negative errno and sets req->out.h.error to -EFAULT.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 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 Aug 12, 2026
No patch confirmed yet.
generic

fuse-uring: fix EFAULT clobber in fuse_uring_commit - kernel/git/stable/linux.git - Linux kernel stable tree

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

fuse-uring: fix EFAULT clobber in fuse_uring_commit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a0a8bc51a13951c5141262bf770eeea3e0b6228
generic

fuse-uring: fix EFAULT clobber in fuse_uring_commit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0483fffdeeb363f320e6bf5fc0f0306007507306

Vendor Advisories for CVE-2026-64264(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

Data Freshness Timeline

(refreshed 15× in last 7d / 61× 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.

  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 11:10 UTCEG score recompute
  6. 2026-08-27 11:10 UTCGHSA enrichment
  7. 2026-08-26 14:47 UTCEPSS rescore
  8. 2026-08-26 10:39 UTCEG score recompute
  9. 2026-08-26 10:39 UTCGHSA enrichment
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-25 09:30 UTCEG score recompute
  12. 2026-08-25 09:30 UTCGHSA enrichment
  13. 2026-08-24 08:59 UTCGHSA enrichment
  14. 2026-08-23 08:29 UTCEG score recompute
  15. 2026-08-23 08:29 UTCGHSA enrichment
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-22 07:59 UTCEG score recompute
  18. 2026-08-22 07:59 UTCGHSA enrichment
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-21 07:29 UTCEG score recompute
  21. 2026-08-21 07:29 UTCGHSA enrichment
  22. 2026-08-20 22:55 UTCEPSS rescore
  23. 2026-08-20 06:59 UTCEG score recompute
  24. 2026-08-20 06:59 UTCGHSA enrichment
  25. 2026-08-19 17:04 UTCEPSS rescore
Show 54 more
  1. 2026-08-19 06:28 UTCEG score recompute
  2. 2026-08-19 06:28 UTCGHSA enrichment
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-18 05:52 UTCEG score recompute
  5. 2026-08-18 05:52 UTCGHSA enrichment
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 05:22 UTCGHSA enrichment
  8. 2026-08-16 18:24 UTCEG score recompute
  9. 2026-08-16 18:24 UTCGHSA enrichment
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-15 17:54 UTCEG score recompute
  12. 2026-08-15 17:54 UTCGHSA enrichment
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 17:23 UTCEG score recompute
  15. 2026-08-14 17:23 UTCGHSA enrichment
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-13 16:43 UTCEG score recompute
  18. 2026-08-13 16:43 UTCGHSA enrichment
  19. 2026-08-12 15:55 UTCEG score recompute 5.50
  20. 2026-08-12 15:55 UTCGHSA enrichment
  21. 2026-08-12 15:55 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-10 23:58 UTCGHSA enrichment
  25. 2026-08-09 13:47 UTCEPSS rescore
  26. 2026-08-08 16:37 UTCEPSS rescore
  27. 2026-08-08 03:47 UTCGHSA enrichment
  28. 2026-08-06 13:47 UTCEPSS rescore
  29. 2026-08-05 19:17 UTCEPSS rescore
  30. 2026-08-05 19:17 UTCEPSS rescore
  31. 2026-08-05 07:37 UTCGHSA enrichment
  32. 2026-08-04 15:10 UTCEPSS rescore
  33. 2026-08-03 10:36 UTCEPSS rescore
  34. 2026-08-02 11:26 UTCGHSA enrichment
  35. 2026-08-02 02:27 UTCEPSS rescore
  36. 2026-08-01 04:16 UTCEPSS rescore
  37. 2026-07-30 16:28 UTCEPSS rescore
  38. 2026-07-30 15:16 UTCEG score recompute
  39. 2026-07-30 15:16 UTCGHSA enrichment
  40. 2026-07-30 01:30 UTCEPSS rescore
  41. 2026-07-30 01:30 UTCEPSS rescore
  42. 2026-07-28 23:04 UTCEG score recompute
  43. 2026-07-28 23:04 UTCGHSA enrichment
  44. 2026-07-28 15:37 UTCEPSS rescore
  45. 2026-07-27 14:14 UTCEPSS rescore
  46. 2026-07-26 14:54 UTCEPSS rescore
  47. 2026-07-26 14:54 UTCEPSS rescore
  48. 2026-07-26 02:54 UTCEG score recompute
  49. 2026-07-26 02:54 UTCGHSA enrichment
  50. 2026-07-25 14:18 UTCEPSS rescore
  51. 2026-07-25 14:18 UTCEPSS rescore
  52. 2026-07-25 10:39 UTCNVD update
  53. 2026-07-25 09:41 UTCEG score recompute
  54. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64264?
CVE-2026-64264 is a medium vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: fuse-uring: fix EFAULT clobber in fuseuringcommit copyfromuser() returns the number of bytes not copied as an unsigned residual on failure (1..sizeof(struct fuseoutheader)). fuseuringcommit stores that residual in ssize_t err, sets…
When was CVE-2026-64264 disclosed?
CVE-2026-64264 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-64264 actively exploited?
CVE-2026-64264 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 95.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64264?
CVE-2026-64264 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64264?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64264, 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-64264

Explore →

Is Your Infrastructure Affected by CVE-2026-64264?

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