In the Linux kernel, the following vulnerability has been resolved: netfs: Fix netfs_invalidate_folio() to clear dirty bit if all changes gone If a… (CVE-2026-64064)
A vulnerability in the Linux kernel's netfs subsystem was resolved by fixing netfs_invalidate_folio() to clear the dirty bit when all changes to a folio are removed. Without this fix, truncating a file after a streaming write could leave a folio marked dirty without the associated netfs_folio struct, causing a kernel oops when the folio is read via mmap(). This issue could be reproduced under specific conditions involving streaming writes, truncation, and memory mapping. The fix involves calling folio_cancel_dirty() to clear the dirty flag appropriately.
AI Analysis
Technical Summary
The Linux kernel netfs subsystem had a vulnerability where netfs_invalidate_folio() did not clear the dirty bit if all changes to a folio were removed after truncation. This left the folio in a dirty state without the netfs_folio struct, leading netfs_read_folio() to call netfs_read_gaps(), which expects the struct to be present, causing a kernel oops (crash). The issue arises after streaming writes followed by truncation and memory-mapped reads. The fix calls folio_cancel_dirty() to clear the dirty bit when all dirty data is erased, preventing the invalid state and subsequent crash.
Potential Impact
This vulnerability can cause a kernel oops (crash) when reading a truncated file via mmap() after certain streaming write and truncate operations. This may lead to system instability or denial of service due to kernel crashes. There is no information about privilege escalation or data corruption beyond the crash.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by properly clearing the dirty bit in netfs_invalidate_folio(). Users should apply the official Linux kernel updates that include this fix once available. Patch status is not yet confirmed in this data; check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: netfs: Fix netfs_invalidate_folio() to clear dirty bit if all changes gone If a… (CVE-2026-64064)
Description
A vulnerability in the Linux kernel's netfs subsystem was resolved by fixing netfs_invalidate_folio() to clear the dirty bit when all changes to a folio are removed. Without this fix, truncating a file after a streaming write could leave a folio marked dirty without the associated netfs_folio struct, causing a kernel oops when the folio is read via mmap(). This issue could be reproduced under specific conditions involving streaming writes, truncation, and memory mapping. The fix involves calling folio_cancel_dirty() to clear the dirty flag appropriately.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel netfs subsystem had a vulnerability where netfs_invalidate_folio() did not clear the dirty bit if all changes to a folio were removed after truncation. This left the folio in a dirty state without the netfs_folio struct, leading netfs_read_folio() to call netfs_read_gaps(), which expects the struct to be present, causing a kernel oops (crash). The issue arises after streaming writes followed by truncation and memory-mapped reads. The fix calls folio_cancel_dirty() to clear the dirty bit when all dirty data is erased, preventing the invalid state and subsequent crash.
Potential Impact
This vulnerability can cause a kernel oops (crash) when reading a truncated file via mmap() after certain streaming write and truncate operations. This may lead to system instability or denial of service due to kernel crashes. There is no information about privilege escalation or data corruption beyond the crash.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by properly clearing the dirty bit in netfs_invalidate_folio(). Users should apply the official Linux kernel updates that include this fix once available. Patch status is not yet confirmed in this data; check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-gxmr-cf3v-qq46
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64064"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a92a4a8d598912c23a
Added to database: 07/19/2026, 19:38:17 UTC
Last enriched: 07/19/2026, 19:52:20 UTC
Last updated: 07/20/2026, 17:26:47 UTC
Views: 12
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.