Skip to main content

Linux Kernel CVE-2026-64059

| EUVDEUVD-2026-45632 MEDIUM
2026-07-19 Linux GHSA-3rfc-7v55-gmrf
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.5 MEDIUM

Local write access to a netfs-backed mount required; no confidentiality or integrity impact, only kernel availability loss via ref-leak-induced panic.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative
Red Hat
5.5 MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

6
Metadata Corrected
Sep 02, 2026 - 23:40 vuln.today
tag: Information Disclosure replaced by Denial Of Service
Analysis Generated
Sep 02, 2026 - 23:36 vuln.today
CVSS changed
Sep 02, 2026 - 21:22 NVD
5.5 (MEDIUM)
Patch available
Jul 19, 2026 - 17:03 EUVD
CVE Published
Jul 19, 2026 - 15:39 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 19, 2026 - 15:39 nvd
MEDIUM 5.5

DescriptionNVD

In the Linux kernel, the following vulnerability has been resolved:

netfs: Fix folio->private handling in netfs_perform_write()

Under some circumstances, netfs_perform_write() doesn't correctly manipulate folio->private between NULL, NETFS_FOLIO_COPY_TO_CACHE, pointing to a group and pointing to a netfs_folio struct, leading to potential multiple attachments of private data with associated folio ref leaks and also leaks of netfs_folio structs or netfs_group refs.

Fix this by consolidating the place at which a folio is marked uptodate in one place and having that look at what's attached to folio->private and decide how to clean it up and then set the new group. Also, the content shouldn't be flushed if group is NULL, even if a group is specified in the netfs_group parameter, as that would be the case for a new folio. A filesystem should always specify netfs_group or never specify netfs_group.

The Sashiko auto-review tool noted that it was theoretically possible that the fpos >= ctx->zero_point section might leak if it modified a streaming write folio. This is unlikely, but with a network filesystem, third party changes can happen. It also pointed out that __netfs_set_group() would leak if called multiple times on the same folio from the "whole folio modify section".

AnalysisAI

Reference leaks and memory corruption in the Linux kernel netfs subsystem allow a local unprivileged user to crash the system via crafted write operations on network-backed filesystems. The flaw in netfs_perform_write() incorrectly transitions folio->private between NULL, the NETFS_FOLIO_COPY_TO_CACHE sentinel, netfs_group pointers, and netfs_folio structs, enabling multiple private-data attachments, folio reference leaks, and netfs_group struct leaks that can exhaust kernel resources or trigger a kernel panic. No public exploit exists and EPSS sits at 0.17% (6th percentile), indicating no observed exploitation activity.

Technical ContextAI

The Linux kernel netfs layer (net/netfs/) provides a shared write-path framework consumed by network filesystems such as NFS, CIFS, and CephFS. Within netfs_perform_write(), the folio->private field serves a multipurpose role: it may be NULL, carry the NETFS_FOLIO_COPY_TO_CACHE sentinel value, point to a netfs_group struct (for grouped write coalescing), or point to a netfs_folio struct (for streaming writes). The defect arises from missing cleanup and incorrect conditional logic when transitioning between these states across code paths including the 'whole folio modify' section and the fpos >= ctx->zero_point branch. The Sashiko static-analysis tool independently identified the theoretical leak paths, corroborating the developer's own diagnosis. The CWE is unassigned, but the root cause class is improper reference counting / resource management (closest to CWE-772 or CWE-401). Affected CPE is cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:* from introducing commit 8f52de0077ba3bf41e5d53d67a185700f41efce7.

RemediationAI

Upgrade the Linux kernel to a patched stable release: 6.12.92, 6.18.34, 7.0.11, or 7.1. The upstream fixes are available at git.kernel.org/stable/c/7f040243c74d72b45b22246c7d9e621fbeab44ac (for 7.1), ccde2ac757c713535b224233a296de40efe5212d (for 6.12.92), and the remaining stable-branch commits referenced in the CVE. Ubuntu users should apply USN-8593-1 (https://ubuntu.com/security/notices/USN-8593-1). As a compensating control where patching is not immediately feasible, restrict untrusted local user write access to network filesystem mount points (NFS, CIFS, CephFS) using filesystem ACLs or by remounting affected shares read-only; this eliminates the write path that triggers the defect, with the trade-off of disrupting legitimate write workflows.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-64059 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy