CVE-2026-98138

Source
https://cve.org/CVERecord?id=CVE-2026-98138
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98138.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-98138
Downstream
Published
2026-09-25T10:36:15Z
Modified
2026-09-26T03:48:33Z
Summary
ntfs: do not mark the volume clean in sync_fs when errors were recorded
Details

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.

Database specific
{
    "cna_assigner":  "Linux",
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98138.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
6251f0b0de7d645e3591931ca4c11d8322c1866f
Fixed
ca1f9933eff777a604eb664d0f9ae433b8664cbf
Fixed
0e4c839905418d55bafe571a92533a1d1ac7b0a8

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98138.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
7.1.0
Fixed
7.2.7

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98138.json"