CVE-2026-90200fs/ntfs3: fix integer overflow in MFT cluster validation
- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: fix integer overflow in MFT cluster validation In ntfs_init_from_boot(), the boot sector's MFT cluster numbers are validated against the volume size with: if (mlcn * sct_per_clst >= sectors || mlcn2 * sct_per_clst >= sectors) goto out; mlcn and mlcn2 are u64 fields read directly from the boot sector. sct_per_clst is bounded above by 4096 (true_sectors_per_clst() plus the is_power_of_2() check below it), but the multiplication is done in u64 and wraps when mlcn (or mlcn2) is large enough -- e.g. mlcn near 2^62 with sct_per_clst == 4 wraps to 0, which compares below any non-zero 'sectors', so the check is bypassed and the malformed record is accepted. The accepted mlcn is then used unchanged in sbi->mft.lbo = mlcn << cluster_bits; In practice the resulting reads fail at the block layer (sb_bread() returns NULL via grow_buffers()'s check_mul_overflow() guard), so today this manifests as mount failing in odd places rather than as something more dangerous, but the validation step is still wrong and there is no reason for callers to rely on the block layer to catch a value that should never have been accepted in the first place. Use check_mul_overflow() to compute the two sector positions and fail the mount if either multiplication wraps; this preserves the existing semantics (mlcn * sct_per_clst >= sectors) instead of switching to division (mlcn >= sectors / sct_per_clst), which would tighten the check at edge cases where 'sectors' is not a multiple of sct_per_clst. The check_*_overflow() style is the one ntfs3 already uses for similar on-disk arithmetic in fs/ntfs3/run.c.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 43 days later
· 43 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < 8ecb1525a9520acd3d5ea3e2593e487fd9f143ce
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < f77a8d9fdf58e298b36564a44c27fadc617bdd28
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < 805cc5554b13d045dce9b03c13eaf015418739fd
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < dc6d85de7e2656e56e10ff5ba514f2583a4f612b
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < 169383d8914b8fe03464a83540b5b6de3e7831af
- affected 82cae269cfa953032fbb8980a7d554d60fb00b17 – < c510c63873103a5da6a498fe537bdb5d6f8d03a2
- affected 5.15
- unaffected < 5.15
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/8ecb1525a9520acd3d5ea3e2593e487fd9f143ce (opens in a new tab)
- https://git.kernel.org/stable/c/f77a8d9fdf58e298b36564a44c27fadc617bdd28 (opens in a new tab)
- https://git.kernel.org/stable/c/805cc5554b13d045dce9b03c13eaf015418739fd (opens in a new tab)
- https://git.kernel.org/stable/c/dc6d85de7e2656e56e10ff5ba514f2583a4f612b (opens in a new tab)
- https://git.kernel.org/stable/c/169383d8914b8fe03464a83540b5b6de3e7831af (opens in a new tab)
- https://git.kernel.org/stable/c/c510c63873103a5da6a498fe537bdb5d6f8d03a2 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-81793 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90200)Record last updated .