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

netfs: Fix potential deadlock in write-through mode

Fix netfs_advance_writethrough() to always unlock the supplied folio and to
mark it dirty if it isn't yet written to the end. Unfortunately, it can't
be marked for writeback until the folio is done with as that may cause a
deadlock against mmapped reads and writes.

Even though it has been marked dirty, premature writeback can't occur as
the caller is holding both inode->i_rwsem (which will prevent concurrent
truncation, fallocation, DIO and other writes) and ictx->wb_lock (which
will cause flushing to wait and writeback to skip or wait).

Note that this may be easier to deal with once the queuing of folios is
split from the generation of subrequests.
Published: 2026-07-19
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability is a concurrency flaw in the Linux kernel’s netfs component, where the function netfs_advance_writethrough() may leave a folio locked and dirty during write‑through mode. This causes a deadlock when an mmap read or write holds conflicting locks, potentially blocking the kernel and any user processes that interact with the affected filesystem. The impact is a denial of service because operations that rely on the netfs filesystem can stall indefinitely, though the flaw does not expose data to an attacker.

Affected Systems

All Linux kernel implementations are vulnerable because the advisory lists the generic Linux kernel CPE without version restrictions. The flaw affects the kernel’s netfs component, which is deployed across most distributions and hardware platforms that use the standard kernel and therefore can affect any system running a recent kernel.

Risk and Exploitability

The CVSS score of 5.5 indicates moderate severity, while the EPSS score of less than 1% signifies a very low likelihood of exploitation at present. The vulnerability is not listed in the CISA KEV catalog. The condition required to trigger the deadlock involves concurrent mmap reads and writes to a netfs volume that has the write‑through option enabled, indicating that the attack vector is local – an attacker with user or privileged access could provoke the deadlock by performing such operations. This inference is based on the description’s mention of concurrent mmap activities. Although complex, this scenario would cause a system hang; thus the immediate risk remains modest, yet a patch should not be postponed.

Generated by OpenCVE AI on July 30, 2026 at 20:48 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest kernel update that includes the netfs deadlock fix.
  • If an immediate kernel update is infeasible, mount netfs filesystems without the write‑through option or use an alternative filesystem type.
  • After updating or reconfiguring, reboot the system to clear any stale folio locks.

Generated by OpenCVE AI on July 30, 2026 at 20:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
History

Mon, 20 Jul 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-833
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low


Sun, 19 Jul 2026 16:15:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: netfs: Fix potential deadlock in write-through mode Fix netfs_advance_writethrough() to always unlock the supplied folio and to mark it dirty if it isn't yet written to the end. Unfortunately, it can't be marked for writeback until the folio is done with as that may cause a deadlock against mmapped reads and writes. Even though it has been marked dirty, premature writeback can't occur as the caller is holding both inode->i_rwsem (which will prevent concurrent truncation, fallocation, DIO and other writes) and ictx->wb_lock (which will cause flushing to wait and writeback to skip or wait). Note that this may be easier to deal with once the queuing of folios is split from the generation of subrequests.
Title netfs: Fix potential deadlock in write-through mode
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-07-19T15:39:41.523Z

Reserved: 2026-07-19T07:54:57.030Z

Link: CVE-2026-64062

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

Severity : Low

Publid Date: 2026-07-19T00:00:00Z

Links: CVE-2026-64062 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-07-30T21:00:22Z

Weaknesses