lz4: fix LZ4_decompress_safe_partial read out of bound
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2209fda323e2fd2a2d0885595fd5097717f8d2aa · < eafc0a02391b7b36617b36c97c4b5d6832cf5e24| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
lz4: fix LZ4_decompress_safe_partial read out of bound
When partialDecoding, it is EOF if we've either filled the output buffer or can't proceed with reading an offset for following match.
In some extreme corner cases when compressed data is suitably corrupted, UAF will occur. As reported by KASAN [1], LZ4_decompress_safe_partial may lead to read out of bound problem during decoding. lz4 upstream has fixed it [2] and this issue has been disscussed here [3] before.
current decompression routine was ported from lz4 v1.8.3, bumping lib/lz4 to v1.9.+ is certainly a huge work to be done later, so, we'd better fix it first.
[1] https://lore.kernel.org/all/000000000000830d1205cf7f0477@google.com/ [2] https://github.com/lz4/lz4/commit/c5d6f8a8be3927c0bec91bcc58667a6cfad244ad# [3] https://lore.kernel.org/all/CC666AE8-4CA4-4951-B6FB-A2EFDE3AC03B@fb.com/
From the CVE record · Linux
The Linux kernel’s LZ4_decompress_safe_partial routine can read out of bounds while decoding suitably corrupted compressed data; in extreme cases, a use-after-free can occur. The input does not specify whether exploitation requires network or local access, authentication, or user interaction.
Anyone running a Linux kernel that includes the affected LZ4 decompression routine should check their kernel version; affected versions are not specified.