CVE-2026-64062: netfs: Fix potential deadlock in write-through mode
In the Linux kernel, the following vulnerability has been resolved:
netfs: Fix potential deadlock in write-through mode
Fix netfs_advance_writethrough() to always unlock the supplied folio and to
mark it dirty if it isn't yet written to the end. Unfortunately, it can't
be marked for writeback until the folio is done with as that may cause a
deadlock against mmapped reads and writes.
Even though it has been marked dirty, premature writeback can't occur as
the caller is holding both inode->i_rwsem (which will prevent concurrent
truncation, fallocation, DIO and other writes) and ictx->wb_lock (which
will cause flushing to wait and writeback to skip or wait).
Note that this may be easier to deal with once the queuing of folios is
split from the generation of subrequests.
Security readout for executives and security teams
Plain-English summary
CVE-2026-64062 is a Linux kernel netfs bug where write-through file operations can deadlock, potentially hanging affected workloads using netfs-backed storage. The sources do not provide CVSS, severity, proof of exploitation, or full distribution impact, so urgency depends on affected kernel exposure and network filesystem use.
Executive priority
Track as an availability-focused kernel issue, not a confirmed exploited emergency. Prioritize patch planning for Linux systems that rely on netfs-backed storage, while waiting for vendor severity and distribution-specific guidance.
Technical view
The fix changes netfs_advance_writethrough() so the supplied folio is always unlocked and marked dirty when not fully written. The CVE text says marking it for writeback too early can deadlock against mmapped reads/writes; existing locks prevent premature writeback during the caller’s critical section.
Likely exposure
Exposure is most likely on Linux systems running affected kernel builds that exercise netfs write-through behavior. The provided version metadata is limited and somewhat ambiguous, so teams should confirm against their exact kernel package, branch, and distribution advisory.
Exploitation context
The bundle does not show CISA KEV listing, public exploitation, exploit code, or attack prerequisites. Based on the description, the primary impact appears to be availability risk through a kernel deadlock, but externally triggerable conditions are not established by the provided sources.
Researcher notes
Useful validation centers on code lineage: whether the running kernel contains vulnerable netfs_advance_writethrough() behavior and lacks the stable commits. The public bundle does not include a CVSS vector, CWE, reproducer, affected distro matrix, or exploitability assessment.
Mitigation direction
Apply vendor kernel updates that include the referenced stable fixes.
If no package exists, monitor Linux and distribution advisories for backports.
Prioritize systems using netfs-backed storage or write-through workloads.
Schedule reboots where required for kernel update activation.
Validation and detection
Inventory running kernel versions across Linux hosts.
Check package changelogs for CVE-2026-64062 or referenced fix commits.
Identify systems using netfs-backed or network filesystem workloads.
Confirm patched kernels are active after reboot or live patching.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-64062 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jul 19, 2026, 15:39 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.