In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before returning from fuse_ref_folio() fuse_ref_folio()… (CVE-2026-64266)
In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before returning from fuse_ref_folio() fuse_ref_folio() unlocks the request but does not re-lock it before returning. fuse_chan_abort() can end the request and the async end callback (eg fuse_writepage_free()) can free the args while the subsequent copy chain logic after fuse_ref_folio() accesses them, leading to use-after-free issues. Fix this by locking the request in fuse_ref_folio() before returning.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's FUSE implementation involves fuse_ref_folio() unlocking a request without re-locking it before returning. This allowed fuse_chan_abort() to end the request and trigger asynchronous callbacks that could free memory still in use by subsequent copy chain logic, resulting in use-after-free conditions. The fix involved modifying fuse_ref_folio() to re-lock the request before returning, preventing premature freeing of resources.
Potential Impact
This vulnerability could lead to use-after-free conditions within the kernel, potentially causing system instability or crashes. The information does not specify any known exploitation in the wild or direct privilege escalation, but use-after-free bugs in kernel code can be serious if exploited.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to re-lock the request before returning from fuse_ref_folio(). Users should apply the official kernel updates that include this patch once available. Patch status is not yet confirmed in this data; check the vendor or Linux kernel advisories for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before returning from fuse_ref_folio() fuse_ref_folio()… (CVE-2026-64266)
Description
In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before returning from fuse_ref_folio() fuse_ref_folio() unlocks the request but does not re-lock it before returning. fuse_chan_abort() can end the request and the async end callback (eg fuse_writepage_free()) can free the args while the subsequent copy chain logic after fuse_ref_folio() accesses them, leading to use-after-free issues. Fix this by locking the request in fuse_ref_folio() before returning.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's FUSE implementation involves fuse_ref_folio() unlocking a request without re-locking it before returning. This allowed fuse_chan_abort() to end the request and trigger asynchronous callbacks that could free memory still in use by subsequent copy chain logic, resulting in use-after-free conditions. The fix involved modifying fuse_ref_folio() to re-lock the request before returning, preventing premature freeing of resources.
Potential Impact
This vulnerability could lead to use-after-free conditions within the kernel, potentially causing system instability or crashes. The information does not specify any known exploitation in the wild or direct privilege escalation, but use-after-free bugs in kernel code can be serious if exploited.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to re-lock the request before returning from fuse_ref_folio(). Users should apply the official kernel updates that include this patch once available. Patch status is not yet confirmed in this data; check the vendor or Linux kernel advisories for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-x828-8hm7-w4xw
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64266"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420e9c2644c7f80865f9
Added to database: 07/25/2026, 23:09:02 UTC
Last enriched: 07/25/2026, 23:40:59 UTC
Last updated: 09/07/2026, 10:52:10 UTC
Views: 68
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.