Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 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

CVSS scores of CVE-2026-89616, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVDNVD · Received3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
0.41% · top 64% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected 4342306f0f0d5ff4315a204d315c1b51b914fca5 – < 7d60a4c49af4d5cb88aa7cbf998d0408bd415055
    • affected 4342306f0f0d5ff4315a204d315c1b51b914fca5 – < cd40eee4923d104ebec9ac7513b971bc441e431d
    • affected 4342306f0f0d5ff4315a204d315c1b51b914fca5 – < 77d8efd04745cda23858546afdbd9d07b591758e
    • affected 4342306f0f0d5ff4315a204d315c1b51b914fca5 – < 0f699ddb290a24b37e1bc9bf1e3c9dbccf564bea
    • affected 4342306f0f0d5ff4315a204d315c1b51b914fca5 – < 376ee45659a4b943df672ad275c63da00655f929
    • affected 4342306f0f0d5ff4315a204d315c1b51b914fca5 – < 4a1b39b2e10eb8de86265e80cf2be4396bc1dce4
    • affected 4342306f0f0d5ff4315a204d315c1b51b914fca5 – < 35d1ea92c7d946e2ebdbe36cdb2c969c8704bebd
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89616 badge
[![CVE-2026-89616](https://cveledger.app/badge/CVE-2026-89616.svg)](https://cveledger.app/cve/CVE-2026-89616)

Record last updated .