CVE-2026-80892

erofs: cap LZMA stream pool size

N/A
Published: September 4, 2026 at 05:11 PM UTC
Updated: September 4, 2026 at 06:36 PM 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
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

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

5.16 ≤ v < 6.1.1845.16 ≤ v < 6.12.1035.16 ≤ v < 6.18.445.16 ≤ v < 6.6.1515.16 ≤ v < 7.1.85.16 ≤ v < 7.25.16622ceaddb7649ca328832f50ba1400af778d75fa
Vendor states this is fixed in 0c676903cb2a61992ded8e7907609cc6b0f11744 (fixed)
Vendor states this is fixed in 5aaa06dfc10f8398c8807453dbec738ea9af10e4 (fixed)
Vendor states this is fixed in 682cb3ece37fc5141e73bc726ccf4adb833e5189 (fixed)
Vendor states this is fixed in c9b47e6b23114e939b17f818471c7a46e59006e7 (fixed)
Vendor states this is fixed in e52da169b8c0d19bb2d803f2a07fe0e5a00462d6 (fixed)
Vendor states this is fixed in e8b3d09aa8889dda9be9cbb3d2f0218c4b9acde4 (fixed)
Vendor states this is fixed in 5.16 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (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.

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