CVE-2026-98135: Linux kernel · ntfs: reject invalid sectors_per_cluster in the boot sector
Affects Linux kernelSource CVE Database V5
Not known to be exploited : upgrade to 323751a604e7533fa473874d999371592a614207 or 7524c3145a3bac92bebbc47a29c007f1d874c9b3 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 323751a604e7533fa473874d999371592a614207, 7524c3145a3bac92bebbc47a29c007f1d874c9b3
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 323751a604e7533fa473874d999371592a614207 or 7524c3145a3bac92bebbc47a29c007f1d874c9b3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel, rejecting any non-power-of-two sectors_per_cluster values in the NTFS boot sector. Users should update to the fixed kernel versions identified by the commits 323751a604e7533fa473874d999371592a614207 and 7524c3145a3bac92bebbc47a29c007f1d874c9b3 to remediate this issue.
Description
A vulnerability in the Linux kernel's NTFS driver allowed invalid sectors_per_cluster values in the boot sector to be accepted, leading to undefined behavior due to an out-of-bounds shift operation. The issue was fixed by rejecting any non-power-of-two sectors_per_cluster values.