LiveActive security incident?Get immediate response
CVE Record

CVE-2026-64060: netfs: Fix leak of request in netfs_write_begin() error handling

In the Linux kernel, the following vulnerability has been resolved: netfs: Fix leak of request in netfs_write_begin() error handling Fix netfs_write_begin() to not leak our ref on the request in the event that we get an error from netfs_wait_for_read().

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel defect where an error path can fail to release an internal request object. In business terms, it is a resource-leak bug, not a documented remote takeover. The public bundle does not provide severity, CVSS, exploitation details, or distribution-specific advisories.

Executive priority

Treat this as a kernel maintenance item pending vendor scoring. Do not ignore it, but avoid emergency escalation unless your Linux vendor rates it higher or confirms material exposure in critical systems.

Technical view

The fix changes netfs_write_begin() so it does not leak its request reference when netfs_wait_for_read() returns an error. The source identifies Linux kernel netfs write-begin error handling, but does not state impact class, prerequisites, privileges, CVSS, CWE, or affected distributions.

Likely exposure

Exposure appears limited to Linux kernels containing the affected netfs code and versions identified in the CVE bundle. The sources do not identify specific Linux distributions, configurations, applications, or filesystem usage requirements.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. It also provides no exploitability analysis, proof-of-concept status, attack vector, or weaponized details.

Researcher notes

The available evidence only supports a request reference leak in netfs_write_begin() error handling. The unusual affected-version data should be reconciled against kernel stable commits and downstream distribution advisories before making exposure claims.

Mitigation direction

  • Apply kernel updates that include the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes.
  • Track vendor guidance because no standalone mitigation is named.
  • Prioritize internet-facing or critical Linux fleets once vendor severity is available.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Compare installed kernels with vendor advisories and fixed stable commits.
  • Confirm whether distro packages include the referenced backports.
  • Record systems that rely on netfs-related write paths if identifiable.
Prepared
Confidence
medium
Sources
5

Public sources used

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-64060 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4090b31422a6f24dfe701e31ffec7ba5804a7e2f, 4090b31422a6f24dfe701e31ffec7ba5804a7e2f, 4090b31422a6f24dfe701e31ffec7ba5804a7e2funaffected
LinuxLinux5.18, 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.