CVE - CVE-2023-52497

CVE-ID
CVE-2023-52497	Learn more at National Vulnerability Database (NVD) • CVSS Severity Rating • Fix Information • Vulnerable Software Versions • SCAP Mappings • CPE Information
Description
In the Linux kernel, the following vulnerability has been resolved: erofs: fix lz4 inplace decompression Currently EROFS can map another compressed buffer for inplace decompression, that was used to handle the cases that some pages of compressed data are actually not in-place I/O. However, like most simple LZ77 algorithms, LZ4 expects the compressed data is arranged at the end of the decompressed buffer and it explicitly uses memmove() to handle overlapping: __________________________________________________________ \|_ direction of decompression --> ____ \|_ compressed data _\| Although EROFS arranges compressed data like this, it typically maps two individual virtual buffers so the relative order is uncertain. Previously, it was hardly observed since LZ4 only uses memmove() for short overlapped literals and x86/arm64 memmove implementations seem to completely cover it up and they don't have this issue. Juhyung reported that EROFS data corruption can be found on a new Intel x86 processor. After some analysis, it seems that recent x86 processors with the new FSRM feature expose this issue with "rep movsb". Let's strictly use the decompressed buffer for lz4 inplace decompression for now. Later, as an useful improvement, we could try to tie up these two buffers together in the correct order.
References
Note: References are provided for the convenience of the reader to help distinguish between vulnerabilities. The list is not intended to be complete.
MISC:https://git.kernel.org/stable/c/33bf23c9940dbd3a22aad7f0cda4c84ed5701847 URL:https://git.kernel.org/stable/c/33bf23c9940dbd3a22aad7f0cda4c84ed5701847 MISC:https://git.kernel.org/stable/c/3c12466b6b7bf1e56f9b32c366a3d83d87afb4de URL:https://git.kernel.org/stable/c/3c12466b6b7bf1e56f9b32c366a3d83d87afb4de MISC:https://git.kernel.org/stable/c/77cbc04a1a8610e303a0e0d74f2676667876a184 URL:https://git.kernel.org/stable/c/77cbc04a1a8610e303a0e0d74f2676667876a184 MISC:https://git.kernel.org/stable/c/a0180e940cf1aefa7d516e20b259ad34f7a8b379 URL:https://git.kernel.org/stable/c/a0180e940cf1aefa7d516e20b259ad34f7a8b379 MISC:https://git.kernel.org/stable/c/bffc4cc334c5bb31ded54bc3cfd651735a3cb79e URL:https://git.kernel.org/stable/c/bffc4cc334c5bb31ded54bc3cfd651735a3cb79e MISC:https://git.kernel.org/stable/c/f36d200a80a3ca025532ed60dd1ac21b620e14ae URL:https://git.kernel.org/stable/c/f36d200a80a3ca025532ed60dd1ac21b620e14ae
Assigning CNA
kernel.org
Date Record Created
20240220	Disclaimer: The record creation date may reflect when the CVE ID was allocated or reserved, and does not necessarily indicate when this vulnerability was discovered, shared with the affected vendor, publicly disclosed, or updated in CVE.
Phase (Legacy)
Assigned (20240220)
Votes (Legacy)

Comments (Legacy)

Proposed (Legacy)
N/A
This is an record on the CVE List, which provides common identifiers for publicly known cybersecurity vulnerabilities.
Search CVE Using Keywords: You can also search by reference using the CVE Reference Maps.
For More Information: CVE Request Web Form (select "Other" from dropdown)