CVE-2026-97605

Published: September 25th, 2026
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.
Unknown
CVSS v2:

Status

DocFilters Release Package State Justification Comment
22.3 lzma (17.01) Needs Triage
22.2 lzma (17.01) Needs Triage
22.1 lzma (17.01) Needs Triage
21.11 lzma (17.01) Needs Triage
21.8 lzma (17.01) Needs Triage
21.5.0 lzma (17.01) Needs Triage
21.2.0 lzma (17.01) Needs Triage
11.4.19.3667 lzma (17.01) Needs Triage
11.4.18.3599 lzma (17.01) Needs Triage
11.4.16.3445 lzma (17.01) Needs Triage
11.4.15.3368 lzma (17.01) Needs Triage
11.4.14.3263 lzma (17.01) Needs Triage
11.4.13.3179 lzma (17.01) Needs Triage
11.4.12.3054 lzma (17.01) Needs Triage
11.4.11.3040 lzma (17.01) Needs Triage
11.4.11.2990 lzma (17.01) Needs Triage
11.4.10.2934 lzma (17.01) Needs Triage
11.4.9.2878 lzma (17.01) Needs Triage
11.4.8.2822 lzma (17.01) Needs Triage

Severity score breakdown

References