# um: Fix out-of-bounds read in LDT setup

CVE record · `CVE-2022-49395`

- **Identifiers:** `CVE-2022-49395`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-125](https://cwe.mitre.org/data/definitions/125.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 26 Feb 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 02:11 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `858259cf7d1c443c836a2022b78cb281f0a9b95e to before 668ca34a428d6ffc0f99a1a6a9b661a288d4183b` (git)
  - affected: `858259cf7d1c443c836a2022b78cb281f0a9b95e to before ef1dc929a1e5fa1b2d842256db9fb8710d3be910` (git)
  - affected: `858259cf7d1c443c836a2022b78cb281f0a9b95e to before 3549ab4b962cf619e8c55484a0d870a34b3f845f` (git)
  - affected: `858259cf7d1c443c836a2022b78cb281f0a9b95e to before 9caad70819aef3431abaf73ba5163b55b161aba0` (git)
  - affected: `858259cf7d1c443c836a2022b78cb281f0a9b95e to before cf0dabc37446c5ee538ae7b4c467ab0e53fa5463` (git)
  - affected: `858259cf7d1c443c836a2022b78cb281f0a9b95e to before 10995a382271254bd276627ec74136da4a23c4a6` (git)
  - affected: `858259cf7d1c443c836a2022b78cb281f0a9b95e to before 24ca648bf5f72ed8878cf09b5d4431935779681e` (git)
  - affected: `858259cf7d1c443c836a2022b78cb281f0a9b95e to before 91e5ba2af2d729d5126aefd5aa3eadc69b8426e5` (git)
  - affected: `858259cf7d1c443c836a2022b78cb281f0a9b95e to before 2a4a62a14be1947fa945c5c11ebf67326381a568` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `2.6.15`
  - unaffected: `before 2.6.15` (semver)
  - unaffected: `4.9.318 to 4.9.*, inclusive` (semver)
  - unaffected: `4.14.283 to 4.14.*, inclusive` (semver)
  - unaffected: `4.19.247 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.198 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.121 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.46 to 5.15.*, inclusive` (semver)
  - unaffected: `5.17.14 to 5.17.*, inclusive` (semver)
  - unaffected: `5.18.3 to 5.18.*, inclusive` (semver)
  - unaffected: `5.19 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 7.1 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0029, the 21st percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 26 Feb 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2022-49395](https://www.cve.org/CVERecord?id=CVE-2022-49395)
- [NVD: CVE-2022-49395](https://nvd.nist.gov/vuln/detail/CVE-2022-49395)

### References from the CNA

- <https://git.kernel.org/stable/c/668ca34a428d6ffc0f99a1a6a9b661a288d4183b>
- <https://git.kernel.org/stable/c/ef1dc929a1e5fa1b2d842256db9fb8710d3be910>
- <https://git.kernel.org/stable/c/3549ab4b962cf619e8c55484a0d870a34b3f845f>
- <https://git.kernel.org/stable/c/9caad70819aef3431abaf73ba5163b55b161aba0>
- <https://git.kernel.org/stable/c/cf0dabc37446c5ee538ae7b4c467ab0e53fa5463>
- <https://git.kernel.org/stable/c/10995a382271254bd276627ec74136da4a23c4a6>
- <https://git.kernel.org/stable/c/24ca648bf5f72ed8878cf09b5d4431935779681e>
- <https://git.kernel.org/stable/c/91e5ba2af2d729d5126aefd5aa3eadc69b8426e5>
- <https://git.kernel.org/stable/c/2a4a62a14be1947fa945c5c11ebf67326381a568>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-49395>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-49395/>. Everything for agents: <https://agentprime.io/llms.txt>.
