CVE-2026-90117

published 17 Sep 2026 · updated 19 Oct 2026

ntfs: validate usa_ofs before preserving the update sequence number

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 81684340963da2e898eabb8c1e274433d9375bc6 and Kernel ea5a3c30710710c1dc5e483d3313309ec2e868f7.

In the Linux kernel, the following vulnerability has been resolved: ntfs: validate usa_ofs before preserving the update sequence number When ntfs_mft_record_alloc() reuses a free mft record it reads the old update sequence number straight from the on-disk record: usn = *(__le16 *)((u8 *)m + le16_to_cpu(m->usa_ofs)); Here m points into the raw $MFT page-cache folio, which still holds unvalidated, MST-protected bytes: the folio is read by a plain iomap_read_folio() and neither post_read_mst_fixup() nor ntfs_mft_record_check() has run on it (both work on private copies). m->usa_ofs is therefore an untrusted u16, and a corrupted record can put it past the end of the record so the two-byte read lands outside the folio. Reading such a record while creating a file gives, under KASAN: BUG: KASAN: use-after-free in ntfs_mft_record_alloc+... Read of size 2 at addr ... ntfs_mft_record_alloc -> __ntfs_create -> ntfs_create -> path_openat Only preserve the old update sequence number when usa_ofs is even and in range, mirroring the check ntfs_mft_record_check() already applies; otherwise leave usn zero, which the existing restore below skips.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=7.1, >=495e90fa334828d4119061e2726af51d0a0fb4ed <81684340963da2e898eabb8c1e274433d9375bc6, >=495e90fa334828d4119061e2726af51d0a0fb4ed <ea5a3c30710710c1dc5e483d3313309ec2e868f781684340963da2e898eabb8c1e274433d9375bc6, ea5a3c30710710c1dc5e483d3313309ec2e868f7

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-90117 severity on Zeptric[![CVE-2026-90117](https://zeptric.io/badge/cve/CVE-2026-90117.svg)](https://zeptric.io/cve/CVE-2026-90117)