Local file corruption via misordered LZ4 buffers
Published Feb 29, 2024 · Updated Aug 5, 2026
Out-of-bounds write in Linux kernel EROFS allows local users to corrupt decompressed file data through reads of LZ4-compressed files. The overlap handler maps compressed input and output as separate virtual buffers whose uncertain ordering violates LZ4 memmove assumptions. Reachability requires a mounted compressed EROFS filesystem and is exposed most clearly on FSRM-capable x86 processors, where corrupted page-cache contents can disrupt the system until reboot.
Summary
What happened
Out-of-bounds write in Linux kernel EROFS allows local users to corrupt decompressed file data through reads of LZ4-compressed files. The overlap handler maps compressed input and output as separate virtual buffers whose uncertain ordering violates LZ4 memmove assumptions. Reachability requires a mounted compressed EROFS filesystem and is exposed most clearly on FSRM-capable x86 processors, where corrupted page-cache contents can disrupt the system until reboot.
The record
- CVE
- CVE-2023-52497
- Published
- Feb 29, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0ffd71bcc3a03ebb3551661a36052488369c4de9 <33bf23c9940dbd3a22aad7f0cda4c84ed5701847
- Affected versionversion=0ffd71bcc3a03ebb3551661a36052488369c4de9 <3c12466b6b7bf1e56f9b32c366a3d83d87afb4de
- Affected versionversion=0ffd71bcc3a03ebb3551661a36052488369c4de9 <77cbc04a1a8610e303a0e0d74f2676667876a184
- Affected versionversion=0ffd71bcc3a03ebb3551661a36052488369c4de9 <9ff2d260b25df6fe1341a79113d88fecf6bd553e
- Affected versionversion=0ffd71bcc3a03ebb3551661a36052488369c4de9 <a0180e940cf1aefa7d516e20b259ad34f7a8b379
- Affected versionversion=0ffd71bcc3a03ebb3551661a36052488369c4de9 <bffc4cc334c5bb31ded54bc3cfd651735a3cb79e
- Affected versionversion=0ffd71bcc3a03ebb3551661a36052488369c4de9 <f36d200a80a3ca025532ed60dd1ac21b620e14ae
- Affected versionversion=5.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo