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-97605erofs: preserve LZMA decoders on resize failure

Description

In the Linux kernel, the following vulnerability has been resolved: erofs: preserve LZMA decoders on resize failure The pool-resize path frees each stream's old decoder before allocating its replacement. If an allocation fails after some streams have already been replaced, the failed stream is put back on the list with state == NULL. z_erofs_lzma_max_dictsize is still advanced as if the whole pool had been resized. An existing LZMA mount can select the broken stream and pass NULL to xz_dec_microlzma_reset(). A retry at the same size also skip another resize attempt. Since the global maximum was advanced, thus, the invalid state is left unrepaired. Allocate each replacement before freeing the old decoder, temporarily retaining one old decoder during allocation. Stop at the first failure and advance z_erofs_lzma_max_dictsize only after all streams satisfy the request. Record each stream's dictionary capacity so retries can skip streams already enlarged before a partial failure.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 622ceaddb7649ca328832f50ba1400af778d75fa – < 164cdbd7ac748c4df1a0c9b435286835668c1f33
    • affected 622ceaddb7649ca328832f50ba1400af778d75fa – < db0c3465b54a16debc089b2b3bda251d26c953d0
    • affected 622ceaddb7649ca328832f50ba1400af778d75fa – < 604ce546e1b9f35b1f45588004f53fac6b2869c1
    • affected 622ceaddb7649ca328832f50ba1400af778d75fa – < 0b3c8c39e50249470f00a5f73c288b95a55ab576
    • affected 622ceaddb7649ca328832f50ba1400af778d75fa – < 38e9e07ac02a9453a117410776f1502a9980997e
    • affected 622ceaddb7649ca328832f50ba1400af778d75fa – < 617d0d8d199ba1790c94310fd75a22d01c97a8d6
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .