Skip to content
Noroxi
CVE-2026-64265· NVD / CVE Program· CNA Linux

fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1d8ecd0cd696a5df0b2f72046a4ccee5d2a8ec2c, 7366e6f4d2b4c7002b13fb01219e83679dad4127, 893479015cb6442fd389d3b553ab3036c9541715.

Low priority for now. Upgrade to Linux Linux 1d8ecd0cd696a5df0b2f72046a4ccee5d2a8ec2c, 7366e6f4d2b4c7002b13fb01219e83679dad4127, 893479015cb6442fd389d3b553ab3036c9541715 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jul 25, 2026
Updated
Aug 17, 2026
EPSS
0.1% · 6th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-64265

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.9 and later · before 6.12.96
  • linux linux kernel6.13 and later · before 6.18.39
  • linux linux kernel6.19 and later · before 7.1.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.9affected
    • 760eac73f9f69aa28fcb3050b4946c2dcc656d12 and later · before 1d8ecd0cd696a5df0b2f72046a4ccee5d2a8ec2caffected · git
    • 760eac73f9f69aa28fcb3050b4946c2dcc656d12 and later · before 7366e6f4d2b4c7002b13fb01219e83679dad4127affected · git
    • 760eac73f9f69aa28fcb3050b4946c2dcc656d12 and later · before 893479015cb6442fd389d3b553ab3036c9541715affected · git
    • 760eac73f9f69aa28fcb3050b4946c2dcc656d12 and later · before f8fce75fedf73ac72aa09163deb8f4291fdcaad2affected · git
    • before 6.9not affected · semver
    • 6.12.96 and later · up to and including 6.12.*not affected · semver
    • 6.18.39 and later · up to and including 6.18.*not affected · semver
    • 7.1.4 and later · up to and including 7.1.*not affected · semver
    • 7.2 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linux-6.12before 6.12.100-1~deb12u16.12.100-1~deb12u1
Debian:13linuxbefore 6.12.96-16.12.96-1
Debian:14linuxbefore 7.1.4-17.1.4-1
Red Hat:enterprise_linux:10.2kernelbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64kbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-corebefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debugbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debug-corebefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debug-debuginfobefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debug-develbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debug-devel-matchedbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debug-modulesbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debug-modules-corebefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debug-modules-extrabefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-debuginfobefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-develbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-devel-matchedbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-modulesbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-modules-corebefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-64k-modules-extrabefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-abi-stablelistsbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-corebefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-debugbefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2
Red Hat:enterprise_linux:10.2kernel-debug-corebefore 0:6.12.0-211.52.1.el10_20:6.12.0-211.52.1.el10_2

+70

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-64263Jul 25, 2026 · fuse-uring: fix moving cancelled entry to ent_in_userspace list
    22Monitor
  • ← EarlierCVE-2026-64264Jul 25, 2026 · fuse-uring: fix EFAULT clobber in fuse_uring_commit
    22Monitor
  • Later →CVE-2026-64267Jul 25, 2026 · fuse: avoid 32-bit prune notification count wrap
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1d8ecd0cd696a5df0b2f72046a4ccee5d2a8ec2cVendor (CNA)
Linux Linux7366e6f4d2b4c7002b13fb01219e83679dad4127Vendor (CNA)
Linux Linux893479015cb6442fd389d3b553ab3036c9541715Vendor (CNA)
Linux Linuxf8fce75fedf73ac72aa09163deb8f4291fdcaad2Vendor (CNA)
debian:linux6.12.96-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
rocky linux:kernel0:6.12.0-211.52.1.el10_2 · Rocky Linux:10Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records