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

ntfs: do not mark the volume clean in sync_fs when errors were recorded

ntfs_put_super() and the remount-read-only path both clear the dirty bit
only when NVolErrors(vol) is false. ntfs_sync_fs() clears it
unconditionally, so any sync() on a volume that recorded an error marks
that volume clean. A volume without this set is then seen as not needing
recovery and it does not run one, so whatever went wrong is never repaired.

This change skips resetting the dirty bit when there are volume errors.

Reproduced on a volume whose $MFTMirr does not match $MFT, which sets the
error flag while leaving the mount read-write: after a write and a sync,
the on-disk volume flags read 0x0000 with this driver and 0x0001 with the
guard in place.
Published: 2026-09-25
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Data integrity loss due to untriggered NTFS recovery
Action: Patch now
AI Analysis

Impact

The Linux kernel NTFS driver contains a flaw where ntfs_sync_fs clears the volume dirty flag unconditionally after a sync() operation, even if NVolErrors(vol) is true. This causes the system to believe the volume is clean and skip the automated recovery pass. Consequently, errors that should trigger a crash-consistency cleanup remain unrepaired, potentially leaving data corruption undiscovered. The weakness arises from insufficient error checking during the sync routine, causing the system state to be incorrectly reset (CWE-390).

Affected Systems

All Linux kernel versions that incorporate the unpatched ntfs_sync_fs code are affected. The vulnerability applies to the NTFS file system module included in Linux kernels; any distribution that ships that driver without the mentioned fix is potentially impacted. No specific kernel release is identified in the CVE payload, so all kernels containing the legacy NTFS driver prior to the patch are considered vulnerable.

Risk and Exploitability

The CVSS score of 5.5 indicates moderate severity; the EPSS score of <1% shows a very low probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector requires a local user with root or elevated privileges who can mount an NTFS volume and induce errors (for example, by modifying $MFTMirr). Once errors are logged, an attacker can trigger a sync() to clear the dirty flag and avoid automatic recovery, resulting in silent data corruption rather than remote code execution. Because the flaw only impacts data integrity, the overall risk remains moderate.

Generated by OpenCVE AI on October 8, 2026 at 19:53 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the kernel to a version that includes the ntfs_sync_fs fix.
  • If a kernel upgrade cannot be performed, avoid invoking sync() on NTFS volumes that have reported errors; instead, unmount and remount the volume read‑only to force a recovery check.
  • Enable monitoring of NTFS error logs (e.g., dmesg, syslog) and schedule a manual consistency check (e.g., fsck.ntfs) after any detected errors.

Generated by OpenCVE AI on October 8, 2026 at 19:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 08 Oct 2026 18:00:00 +0000

Type Values Removed Values Added
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:o:linux:linux_kernel:7.3:rc1:*:*:*:*:*:*

Tue, 29 Sep 2026 21:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665
CWE-754

Tue, 29 Sep 2026 13:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-390
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


Fri, 25 Sep 2026 12:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665
CWE-754

Fri, 25 Sep 2026 10:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ntfs: do not mark the volume clean in sync_fs when errors were recorded ntfs_put_super() and the remount-read-only path both clear the dirty bit only when NVolErrors(vol) is false. ntfs_sync_fs() clears it unconditionally, so any sync() on a volume that recorded an error marks that volume clean. A volume without this set is then seen as not needing recovery and it does not run one, so whatever went wrong is never repaired. This change skips resetting the dirty bit when there are volume errors. Reproduced on a volume whose $MFTMirr does not match $MFT, which sets the error flag while leaving the mount read-write: after a write and a sync, the on-disk volume flags read 0x0000 with this driver and 0x0001 with the guard in place.
Title ntfs: do not mark the volume clean in sync_fs when errors were recorded
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-09-25T10:36:15.349Z

Reserved: 2026-09-25T10:25:14.319Z

Link: CVE-2026-98138

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Analyzed

Published: 2026-09-25T11:17:45.273

Modified: 2026-10-08T17:46:19.780

Link: CVE-2026-98138

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-25T00:00:00Z

Links: CVE-2026-98138 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-08T20:00:02Z

Weaknesses