erofs: preserve LZMA decoders on resize failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 622ceaddb7649ca328832f50ba1400af778d75fa · < 617d0d8d199ba1790c94310fd75a22d01c97a8d6| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s EROFS LZMA decoder pool can retain a stream with a NULL decoder if allocation fails during a pool resize. An existing LZMA mount can then select that stream and pass NULL to the decoder reset function. The input does not establish an attacker access path or authentication requirement.
Engineers running Linux kernels with EROFS LZMA mounts should check their kernel version; affected versions were not provided.