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-80892erofs: cap LZMA stream pool size

Description

In the Linux kernel, the following vulnerability has been resolved: erofs: cap LZMA stream pool size fs/erofs/decompressor_lzma.c sizes the module-global MicroLZMA stream pool from num_possible_cpus() when the lzma_streams module parameter is unset, then z_erofs_load_lzma_config() preallocates one image-supplied dictionary per stream, accepting dictionaries up to 8 MiB. On high-CPU systems, a small EROFS image can pin hundreds of MiB of vmalloc-backed decoder state until the erofs module is unloaded. Impact: An EROFS image mounted by the system can pin up to 8 MiB of vmalloc memory per LZMA stream, either as intended or unexpectedly. Bound the default stream count by a new CONFIG_EROFS_FS_ZIP_LZMA_DEFAULT_MAX_STREAMS option, default 16, so the worst-case default preallocation is 128 MiB if the number of CPUs is no less than 16 while preserving the existing per-image dictionary limit. An explicit lzma_streams module parameter is still honoured as-is, so administrators who deliberately size the pool are not affected.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 2 months 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.17% · top 93% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 – < 682cb3ece37fc5141e73bc726ccf4adb833e5189
    • affected 622ceaddb7649ca328832f50ba1400af778d75fa – < e8b3d09aa8889dda9be9cbb3d2f0218c4b9acde4
    • affected 622ceaddb7649ca328832f50ba1400af778d75fa – < 0c676903cb2a61992ded8e7907609cc6b0f11744
    • affected 622ceaddb7649ca328832f50ba1400af778d75fa – < 5aaa06dfc10f8398c8807453dbec738ea9af10e4
    • affected 622ceaddb7649ca328832f50ba1400af778d75fa – < e52da169b8c0d19bb2d803f2a07fe0e5a00462d6
    • affected 622ceaddb7649ca328832f50ba1400af778d75fa – < c9b47e6b23114e939b17f818471c7a46e59006e7
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.151 – ≤ 6.6.*
    • unaffected 6.12.103 – ≤ 6.12.*
    • unaffected 6.18.44 – ≤ 6.18.*
    • unaffected 7.1.8 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .