CVE-2026-64265

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 — 4 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

A fix is available — apply it.

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

fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req

When fuse_resend() moves a request from fpq->processing back to fiq->pending, it sets FR_PENDING and clears FR_SENT but does not remove the requests intr_entry from fiq->interrupts. If the request had FR_INTERRUPTED set from a prior signal, intr_entry remains dangling on fiq->interrupts. When the requesting task then receives a fatal signal, fuse_remove_pending_req() sees FR_PENDING=1, removes the request from fiq->pending and frees it via the refcount path, also without cleaning intr_entry. The stale intr_entry causes use-after-free when fuse_read_interrupt() iterates fiq->interrupts:

  • list_del_init(&req->intr_entry) -> UAF write on freed slab
  • req->in.h.unique -> UAF read, data leaked to userspace

Remove intr_entry from fiq->interrupts in fuse_resend() for interrupted requests before they are placed back on fiq->pending.

Add a WARN_ON if the intr_entry is not empty on request destruction.

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

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (4)

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

fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req - kernel/git/stable/linux.git - Linux kernel stable tree

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

fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/893479015cb6442fd389d3b553ab3036c9541715
generic

fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7366e6f4d2b4c7002b13fb01219e83679dad4127
generic

fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-64265(2)

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

Patch Availability(6)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.4-1

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

Frequently asked(5)

What is CVE-2026-64265?
CVE-2026-64265 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: fuse: clear intrentry in fuseresend and fuseremovepending_req When fuse_resend() moves a request from fpq->processing back to fiq->pending, it sets FRPENDING and clears FRSENT but does not remove the requests intr_entry from…
When was CVE-2026-64265 disclosed?
CVE-2026-64265 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-64265 actively exploited?
CVE-2026-64265 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64265?
CVE-2026-64265 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64265?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64265, 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-64265

Explore →

Is Your Infrastructure Affected by CVE-2026-64265?

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