CVE-2026-64058: netfs: Fix netfs_read_folio() to wait on writeback
In the Linux kernel, the following vulnerability has been resolved:
netfs: Fix netfs_read_folio() to wait on writeback
Fix netfs_read_folio() to wait for an ongoing writeback to complete so that
it can trust the dirty flag and whatever is attached to folio->private
(folio->private may get cleaned up by the collector before it clears the
writeback flag).
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel flaw in network filesystem read handling. A local low-privileged user may be able to trigger serious confidentiality, integrity, and availability impact. It is not remotely exploitable based on the supplied CVSS vector, and no active exploitation is cited in the source bundle.
Executive priority
Treat this as a high-priority kernel maintenance issue, especially for multi-user Linux environments. It is serious because local low-privileged access may lead to full impact, but current supplied evidence does not support emergency internet-wide exploitation claims.
Technical view
The bug is in netfs_read_folio(). It failed to wait for ongoing writeback before trusting folio dirty state and folio->private. The source says folio->private may be cleaned up by a collector before the writeback flag clears, creating unsafe state handling in the kernel netfs path.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel versions or vendor kernels that include the vulnerable netfs code. The supplied affected-version data is incomplete and partly ambiguous, so teams should map their kernel builds to vendor advisories and the referenced stable commits.
Exploitation context
The supplied CVSS vector is local, low-complexity, low-privilege, no user interaction, with high CIA impact. The bundle marks KEV false and provides no cited evidence of active exploitation or public exploit availability.
Researcher notes
Do not assume affected distributions from upstream version strings alone. Validate by commit ancestry and vendor backport status. The key code condition is read-folio behavior racing ongoing writeback and cleanup of folio private data.
Mitigation direction
Track Linux kernel and distribution advisories for CVE-2026-64058.
Update to vendor kernels containing the referenced stable fixes.
Prioritize shared multi-user Linux hosts and systems exposing netfs functionality.
Use normal change windows only where compensating controls reduce local-user risk.
If patching is delayed, restrict untrusted local shell access where practical.
Validation and detection
Inventory Linux kernel versions across servers, workstations, and containers hosts.
Compare running kernels with vendor advisories and referenced stable commits.
Check whether affected systems use network filesystem paths relying on netfs.
Confirm updated kernels are booted, not only installed.
Document exceptions where vendor mapping is not yet available.
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-64058 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.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.