LiveActive security incident?Get immediate response
CVE Record

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).

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
5

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.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-64058Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxee4cdf7ba857a894ad1650d6ab77669cbbfa329e, ee4cdf7ba857a894ad1650d6ab77669cbbfa329e, ee4cdf7ba857a894ad1650d6ab77669cbbfa329eunaffected
LinuxLinux6.12, 0, 6.18.34, 7.0.11, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.