CVE-2026-64068: netfs: Fix missing locking around retry adding new subreqs
In the Linux kernel, the following vulnerability has been resolved:
netfs: Fix missing locking around retry adding new subreqs
Fix netfs_retry_read_subrequests() and netfs_retry_write_stream() to take
the appropriate lock when adding extra subrequests into
stream->subrequests.
Security readout for executives and security teams
Plain-English summary
CVE-2026-64068 is a critical Linux kernel netfs flaw involving unsafe handling of retry subrequests. The source assigns CVSS 9.8, indicating potential full confidentiality, integrity, and availability impact without authentication or user interaction. The public bundle does not prove real-world exploitation.
Executive priority
Treat as urgent for Linux fleet patch governance because the assigned impact is critical. Start with exposed, sensitive, and high-availability systems, while recognizing that the current public evidence does not confirm active exploitation.
Technical view
The bug is missing locking in netfs_retry_read_subrequests() and netfs_retry_write_stream() when adding extra subrequests to stream->subrequests. This is a kernel concurrency defect in Linux netfs. The source links two stable kernel commits as the resolution, but does not describe exploit mechanics.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel builds with the relevant netfs code path present. The bundle lists Linux as affected and includes version markers around 6.10, 7.0.11, and 7.1, but distribution-specific package mapping requires vendor advisories.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. The CVSS vector is network, low complexity, no privileges, and no user interaction, but the bundle provides limited practical exploitation detail.
Researcher notes
The public description is sparse: it identifies a locking defect and the affected functions, but not a CWE, exploit primitive, or affected configuration details. Validation should focus on commit presence, distro backports, and whether workloads can reach netfs retry paths.
Mitigation direction
Apply Linux kernel updates containing the referenced stable fixes.
Check distribution security advisories for fixed package versions.
Prioritize internet-facing or high-trust Linux systems first.
Track CISA KEV and vendor advisories for exploitation updates.
Validation and detection
Inventory Linux kernel versions across production and edge systems.
Confirm whether deployed kernels include the referenced stable commits.
Map distribution package versions to vendor fixed builds.
Review systems using netfs-related functionality for priority handling.
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-64068 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
3Source 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.