CVE Catalog

CVE-2026-98138

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel, ntfs_sync_fs() in the ntfs driver unconditionally clears the dirty bit, whereas ntfs_put_super() and the remount-read-only path only clear it when NVolErrors(vol) is false. As a result, any sync() on a volume that recorded an error marks that volume clean, so no recovery is run.

Risk Assessment

A volume with unresolved errors may be treated as clean and never repaired, leading to persistent filesystem inconsistencies.

Recommendation

Update the Linux kernel to a version containing the fix that skips resetting the dirty bit when volume errors are recorded.

Other vulnerabilities in Linux kernel (ntfs)

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS