CVE-2023-52497

published 29 Feb 2024 · updated 5 Aug 2026

erofs: fix lz4 inplace decompression

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 33bf23c9940dbd3a22aad7f0cda4c84ed5701847, Kernel 3c12466b6b7bf1e56f9b32c366a3d83d87afb4de, Kernel 77cbc04a1a8610e303a0e0d74f2676667876a184 and 4 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.3, >=0ffd71bcc3a03ebb3551661a36052488369c4de9 <33bf23c9940dbd3a22aad7f0cda4c84ed5701847, >=0ffd71bcc3a03ebb3551661a36052488369c4de9 <3c12466b6b7bf1e56f9b32c366a3d83d87afb4de, >=0ffd71bcc3a03ebb3551661a36052488369c4de9 <77cbc04a1a8610e303a0e0d74f2676667876a184, >=0ffd71bcc3a03ebb3551661a36052488369c4de9 <9ff2d260b25df6fe1341a79113d88fecf6bd553e, >=0ffd71bcc3a03ebb3551661a36052488369c4de9 <a0180e940cf1aefa7d516e20b259ad34f7a8b379, >=0ffd71bcc3a03ebb3551661a36052488369c4de9 <bffc4cc334c5bb31ded54bc3cfd651735a3cb79e, >=0ffd71bcc3a03ebb3551661a36052488369c4de9 <f36d200a80a3ca025532ed60dd1ac21b620e14ae33bf23c9940dbd3a22aad7f0cda4c84ed5701847, 3c12466b6b7bf1e56f9b32c366a3d83d87afb4de, 77cbc04a1a8610e303a0e0d74f2676667876a184, 9ff2d260b25df6fe1341a79113d88fecf6bd553e, a0180e940cf1aefa7d516e20b259ad34f7a8b379, bffc4cc334c5bb31ded54bc3cfd651735a3cb79e, f36d200a80a3ca025532ed60dd1ac21b620e14ae

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2023-52497 severity on Zeptric[![CVE-2023-52497](https://zeptric.io/badge/cve/CVE-2023-52497.svg)](https://zeptric.io/cve/CVE-2023-52497)