Skip to main content

Linux Kernel CVE-2026-64156

| EUVDEUVD-2026-45841 MEDIUM
2026-07-19 Linux GHSA-hcxq-wxqg-v33q
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.3 MEDIUM

Race condition under lock contention raises AC to H; skipped writes risking silent data loss warrant I:L alongside A:H.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
SUSE
4.7 MEDIUM
AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
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

5
Analysis Generated
Aug 13, 2026 - 15:33 vuln.today
CVSS changed
Aug 13, 2026 - 15:22 NVD
5.5 (MEDIUM)
Patch available
Jul 19, 2026 - 17:03 EUVD
CVE Published
Jul 19, 2026 - 15:40 nvd
MEDIUM 5.5
CVE Published
Jul 19, 2026 - 15:40 cve.org
UNKNOWN (no severity yet)

DescriptionNVD

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

netfs, afs: Fix write skipping in dir/link writepages

Fix netfs_write_single() and afs_single_writepages() to better handle a write that would be skipped due to lock contention and WB_SYNC_NONE by returning 1 from netfs_write_single() if it skipped and making afs_single_writepages() skip also. If a skip occurs, the inode must be re-marked as the VFS may have cleared the mark.

This is really only theoretical for directories in netfs_write_single() as the only path to that is through afs_single_writepages() that takes the ->validate_lock around it, thereby serialising it.

AnalysisAI

Incorrect writeback state management in the Linux kernel's netfs and AFS subsystems allows a local low-privileged user on an AFS-mounted system to cause filesystem availability degradation. When netfs_write_single() or afs_single_writepages() skips a write due to lock contention under asynchronous writeback (WB_SYNC_NONE), the affected inode loses its dirty mark without the write being rescheduled, meaning data may never be flushed to the AFS server. No public exploit has been identified and the EPSS score of 0.17% at the 6th percentile reflects very low exploitation probability; patched versions are confirmed available across multiple stable kernel branches.

Technical ContextAI

The vulnerability resides in the Linux kernel's netfs layer (network filesystem abstraction) and its AFS (Andrew File System) client implementation. The netfs_write_single() function handles writing a single folio to a network filesystem backend, while afs_single_writepages() coordinates writeback for AFS directory and symlink inodes. Under WB_SYNC_NONE (asynchronous, non-blocking writeback), if a lock cannot be acquired immediately the write may be intentionally skipped - but the bug is that the inode's dirty flag is not re-asserted afterward. The VFS writeback infrastructure, which may have already cleared that flag, will then never retry the write. The developers note this is 'really only theoretical for directories' because afs_single_writepages() holds ->validate_lock around the call, serializing concurrent access. No CWE is formally assigned, but the root cause resembles CWE-664 (Improper Control of a Resource Through its Lifetime) - specifically a missed state re-assertion after a conditional skip. Affected CPE: cpe:2.3:a:linux:linux. Only kernels containing commit 6dd80936618c4ff852d4db73aca400351d9bd9f0 and lacking the fix commits are vulnerable.

RemediationAI

Upgrade to a patched Linux kernel: 6.18.34 or later for the 6.18.x stable branch, 7.0.11 or later for the 7.0.x branch, or any 7.1+ mainline release. The authoritative fix commits are at https://git.kernel.org/stable/c/77bb293049d61e04c12b24ebbffafaf5ab36af90 (6.18.34), https://git.kernel.org/stable/c/9871938f99cc6cb266a77265491660e2375271f5 (7.0.11), and https://git.kernel.org/stable/c/f91e10435c0dd37c48b1b25e6236284f656ddc0c (7.1). Ubuntu users should apply packages from USN-8593-1. For environments where an immediate kernel upgrade is operationally blocked, the most targeted compensating control is to unload the AFS kernel module ('modprobe -r kafs') if AFS is not required - this eliminates the vulnerable code path entirely with no impact on other filesystem types. There is no supported tunable to disable WB_SYNC_NONE selectively for AFS, so module removal is the only practical workaround; its trade-off is loss of AFS connectivity until the kernel is upgraded.

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 Not-Affected

Share

CVE-2026-64156 vulnerability details – vuln.today

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