Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-52497erofs: fix lz4 inplace decompression

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-52497, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
NVDNVD · Modified3.1Medium6.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected 0ffd71bcc3a03ebb3551661a36052488369c4de9 – < 9ff2d260b25df6fe1341a79113d88fecf6bd553e
    • affected 0ffd71bcc3a03ebb3551661a36052488369c4de9 – < a0180e940cf1aefa7d516e20b259ad34f7a8b379
    • affected 0ffd71bcc3a03ebb3551661a36052488369c4de9 – < 77cbc04a1a8610e303a0e0d74f2676667876a184
    • affected 0ffd71bcc3a03ebb3551661a36052488369c4de9 – < 33bf23c9940dbd3a22aad7f0cda4c84ed5701847
    • affected 0ffd71bcc3a03ebb3551661a36052488369c4de9 – < f36d200a80a3ca025532ed60dd1ac21b620e14ae
    • affected 0ffd71bcc3a03ebb3551661a36052488369c4de9 – < bffc4cc334c5bb31ded54bc3cfd651735a3cb79e
    • affected 0ffd71bcc3a03ebb3551661a36052488369c4de9 – < 3c12466b6b7bf1e56f9b32c366a3d83d87afb4de
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • unaffected 5.4.285 – ≤ 5.4.*
    • unaffected 5.10.211 – ≤ 5.10.*
    • unaffected 5.15.150 – ≤ 5.15.*
    • unaffected 6.1.76 – ≤ 6.1.*
    • unaffected 6.6.15 – ≤ 6.6.*
    • unaffected 6.7.3 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-52497 badge
[![CVE-2023-52497](https://cveledger.app/badge/CVE-2023-52497.svg)](https://cveledger.app/cve/CVE-2023-52497)

Record last updated .