Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-52497: erofs: fix lz4 inplace decompression

Noroxi assessment

Priority: Monitor (action score 24/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 33bf23c9940dbd3a22aad7f0cda4c84ed5701847, 3c12466b6b7bf1e56f9b32c366a3d83d87afb4de, 77cbc04a1a8610e303a0e0d74f2676667876a184.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 33bf23c9940dbd3a22aad7f0cda4c84ed5701847, 3c12466b6b7bf1e56f9b32c366a3d83d87afb4de, 77cbc04a1a8610e303a0e0d74f2676667876a184 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.1 · v3.1—No exploit Fix available
Published
Mar 1, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 20th percentile

Report tools

JSON

Action score

24

Monitor

Low priority for now.

CVSS
24 / 40 · 6.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
6.1
CNA · Linux
7.1
1.0 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-52497

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.3 and later · before 5.4.285
  • linux linux kernel5.5 and later · before 5.10.211
  • linux linux kernel5.11 and later · before 5.15.150
  • linux linux kernel5.16 and later · before 6.1.76
  • linux linux kernel6.2 and later · before 6.6.15
  • linux linux kernel6.7 and later · before 6.7.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.3affected
    • 0ffd71bcc3a03ebb3551661a36052488369c4de9 and later · before 9ff2d260b25df6fe1341a79113d88fecf6bd553eaffected · git
    • 0ffd71bcc3a03ebb3551661a36052488369c4de9 and later · before a0180e940cf1aefa7d516e20b259ad34f7a8b379affected · git
    • 0ffd71bcc3a03ebb3551661a36052488369c4de9 and later · before 77cbc04a1a8610e303a0e0d74f2676667876a184affected · git
    • 0ffd71bcc3a03ebb3551661a36052488369c4de9 and later · before 33bf23c9940dbd3a22aad7f0cda4c84ed5701847affected · git
    • 0ffd71bcc3a03ebb3551661a36052488369c4de9 and later · before f36d200a80a3ca025532ed60dd1ac21b620e14aeaffected · git
    • 0ffd71bcc3a03ebb3551661a36052488369c4de9 and later · before bffc4cc334c5bb31ded54bc3cfd651735a3cb79eaffected · git
    • 0ffd71bcc3a03ebb3551661a36052488369c4de9 and later · before 3c12466b6b7bf1e56f9b32c366a3d83d87afb4deaffected · git
    • before 5.3not affected · semver
    • 5.4.285 and later · up to and including 5.4.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:10linux-5.10before 5.10.216-1~deb10u15.10.216-1~deb10u1
Debian:11linuxbefore 5.10.216-15.10.216-1
Debian:12linuxbefore 6.1.76-16.1.76-1
Debian:13linuxbefore 6.6.15-16.6.15-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2021-47067Feb 29, 2024 · soc/tegra: regulators: Fix locking up when voltage-spread is out of range
    22Monitor
  • ← EarlierCVE-2021-47068Feb 29, 2024 · net/nfc: fix use-after-free llcp_sock_bind/connect
    31Monitor
  • Later →CVE-2021-47069Mar 1, 2024 · ipc/mqueue, msg, sem: avoid relying on a stack reference past its expiry
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux33bf23c9940dbd3a22aad7f0cda4c84ed5701847Vendor (CNA)
Linux Linux3c12466b6b7bf1e56f9b32c366a3d83d87afb4deVendor (CNA)
Linux Linux77cbc04a1a8610e303a0e0d74f2676667876a184Vendor (CNA)
Linux Linux9ff2d260b25df6fe1341a79113d88fecf6bd553eVendor (CNA)
Linux Linuxa0180e940cf1aefa7d516e20b259ad34f7a8b379Vendor (CNA)
Linux Linuxbffc4cc334c5bb31ded54bc3cfd651735a3cb79eVendor (CNA)
Linux Linuxf36d200a80a3ca025532ed60dd1ac21b620e14aeVendor (CNA)
debian:linux6.1.76-1 · Debian:12Package registry (OSV)
debian:linux-5.105.10.216-1~deb10u1 · Debian:10Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
High

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records