# CVE-2022-50746: erofs: validate the extent length for uncompressed pclusters

> A use-after-free vulnerability in the Linux kernel's EROFS filesystem allows attackers to cause denial of service or potentially execute code via a crafted image.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 15 Oct 2026
- **Also known as:** DEBIAN-CVE-2022-50746, GHSA-9rf3-hx86-5f4p, ROOT-OS-DEBIAN-11-CVE-2022-50746, ROOT-OS-UBUNTU-2204-CVE-2022-50746, UBUNTU-CVE-2022-50746

## What is CVE-2022-50746?

CVE-2022-50746 is a high-severity use after free vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

erofs: validate the extent length for uncompressed pclusters

syzkaller reported a KASAN use-after-free:
https://syzkaller.appspot.com/bug?extid=2ae90e873e97f1faf6f2

The referenced fuzzed image actually has two issues:
 - m_pa == 0 as a non-inlined pcluster;
 - The logical length is longer than its physical length.

The first issue has already been addressed.  This patch addresses
the second issue by checking the extent length validity.

## Which versions are affected by CVE-2022-50746?


## How do I fix CVE-2022-50746?

Apply the vendor's patch.

## Is CVE-2022-50746 being exploited?

There is no known exploitation of CVE-2022-50746 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50746 and fix it if it is affected.

What it is: CVE-2022-50746 is a high-severity use after free vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50746 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-50746/ (Markdown: https://insights.sbomify.com/CVE-2022-50746/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50746
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50746
- OSV: https://osv.dev/vulnerability/CVE-2022-50746

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-50746/
Summaries are generated and may contain mistakes; the official description above is the record.