CVE-2026-89616

fs/ntfs3: fix info-leak on partial LZNT decompress in ni_read_frame()

HIGH
7.5
CVSS Score
Published: September 11, 2026 at 07:45 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4342306f0f0d5ff4315a204d315c1b51b914fca55.15
Vendor states this is fixed in 0f699ddb290a24b37e1bc9bf1e3c9dbccf564bea (fixed)
Vendor states this is fixed in 35d1ea92c7d946e2ebdbe36cdb2c969c8704bebd (fixed)
Vendor states this is fixed in 376ee45659a4b943df672ad275c63da00655f929 (fixed)
Vendor states this is fixed in 4a1b39b2e10eb8de86265e80cf2be4396bc1dce4 (fixed)
Vendor states this is fixed in 77d8efd04745cda23858546afdbd9d07b591758e (fixed)
Vendor states this is fixed in 7d60a4c49af4d5cb88aa7cbf998d0408bd415055 (fixed)
Vendor states this is fixed in cd40eee4923d104ebec9ac7513b971bc441e431d (fixed)
Vendor states this is fixed in 5.15 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.5HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card