CVE-2026-98137: Linux kernel · ntfs: treat any nonzero dio zero-range return as an error
Affects Linux kernelSource CVE Database V5
Not known to be exploited : upgrade to 56392b0d5290ff2b05fc673bc07803b8ae4cfd1b or 607a9478833db656e7ceac8e9e382fa4acfde545 when convenient.
Data as of 26 Oct 2026, 14:05 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 56392b0d5290ff2b05fc673bc07803b8ae4cfd1b, 607a9478833db656e7ceac8e9e382fa4acfde545
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to 56392b0d5290ff2b05fc673bc07803b8ae4cfd1b or 607a9478833db656e7ceac8e9e382fa4acfde545.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in the Linux kernel commits 56392b0d5290ff2b05fc673bc07803b8ae4cfd1b and 607a9478833db656e7ceac8e9e382fa4acfde545. Users and administrators should update to a Linux kernel version including these commits or later to remediate this issue. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's NTFS driver caused failed zeroing operations during file allocation to be silently ignored, potentially leaving stale data on disk. The flaw was due to improper handling of nonzero return values from ntfs_dio_zero_range(), which never returns positive values but the code only checked for negative errors. This could result in allocated clusters being incorrectly marked as initialized, risking data integrity. The issue has been fixed by treating any nonzero return as an error and aborting the allocation.