CVE-2026-23109

fs/writeback: skip AS_NO_DATA_INTEGRITY mappings in wait_sb_inodes()

Published Feb 4, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

fs/writeback: skip AS_NO_DATA_INTEGRITY mappings in wait_sb_inodes()

Above the while() loop in wait_sb_inodes(), we document that we must wait
for all pages under writeback for data integrity. Consequently, if a
mapping, like fuse, traditionally does not have data integrity semantics,
there is no need to wait at all; we can simply skip these inodes.

This restores fuse back to prior behavior where syncs are no-ops. This
fixes a user regression where if a system is running a faulty fuse server
that does not reply to issued write requests, this causes wait_sb_inodes()
to wait forever.

Analysis

AI-generated

Technical impact

A bug in the Linux kernel’s writeback logic causes the wait_sb_inodes() function to skip data‑integrity checks for filesystems that do not provide them, such as FUSE mounts. When a FUSE server fails to acknowledge write requests, the waiting loop can block indefinitely, resulting in a denial‑of‑service condition that stalls sync operations and can leave higher‑level processes hanging. The weakness is identified as CWE‑835.

Affected Systems

This issue is present in the Linux kernel starting from the 6.19 release candidates through rc6, as indicated by the CPE strings. Any kernel build that incorporates the unchanged writeback code is vulnerable, and upstream stable kernels that eventually receive the patch will also be affected. No specific distribution names were supplied, so all Linux kernel installations that have not applied the fix are at risk.

Risk and Exploitability

The CVSS score of 5.5 places the vulnerability in the medium severity range. The EPSS score of less than 1 % suggests a low chance of exploitation, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires a faulty or malicious FUSE server that the target system mounts, making the attack vector local or remote to the mount point. While the impact is limited to the host executing sync operations, it can lead to resource starvation or a hung system, but does not grant privilege escalation or data theft.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to a patched version (for example 6.19 rc7 or later) or apply the upstream source fix for wait_sb_inodes().
  • If a kernel upgrade cannot be performed immediately, unmount or avoid mounting suspicious FUSE filesystems until the patch is applied, or use sync options that skip sync on those mounts.
  • Verify that any FUSE server you rely on responds to write requests; add health checks or enforce timeouts in the client.
  • Monitor system logs for prolonged sync activity and set alerts on excessive wait times.

Generated by OpenCVE AI on April 17, 2026 at 23:30 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8570-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8594-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8604-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8605-1 Linux kernel (Azure CVM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8570-2 Linux kernel (Oracle) vulnerabilities
Ubuntu USN Ubuntu USN USN-8669-1 Linux kernel (NVIDIA) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-835
CPEs cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:*
Type Values Removed Values Added
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

Moderate

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: fs/writeback: skip AS_NO_DATA_INTEGRITY mappings in wait_sb_inodes() Above the while() loop in wait_sb_inodes(), we document that we must wait for all pages under writeback for data integrity. Consequently, if a mapping, like fuse, traditionally does not have data integrity semantics, there is no need to wait at all; we can simply skip these inodes. This restores fuse back to prior behavior where syncs are no-ops. This fixes a user regression where if a system is running a faulty fuse server that does not reply to issued write requests, this causes wait_sb_inodes() to wait forever.
Title fs/writeback: skip AS_NO_DATA_INTEGRITY mappings in wait_sb_inodes()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-835

    Loop with Unreachable Exit Condition ('Infinite Loop')

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
May 11, 2026, 10:00 PM
Reserved
Jan 13, 2026, 3:37 PM
Status
Analyzed
Published
Feb 4, 2026, 5:16 PM
Modified
Jun 17, 2026, 10:20 AM
Severity
Moderate
Public date
Feb 4, 2026, 12:00 AM