erofs: cap LZMA stream pool size
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 622ceaddb7649ca328832f50ba1400af778d75fa · < c9b47e6b23114e939b17f818471c7a46e59006e7| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's EROFS LZMA decompressor can preallocate up to 8 MiB of vmalloc-backed memory per stream when an EROFS image is mounted. On high-CPU systems, an image can cause hundreds of MiB to remain allocated until the erofs module is unloaded. The input does not specify an attacker's access requirements; mounting the image is the relevant condition.
Teams running Linux kernels with EROFS LZMA support should check their kernel versions against the vendor advisory; affected versions are not specified.