# arm64: set UXN on swapper page tables

CVE record · `CVE-2022-50232`

- **Identifiers:** `CVE-2022-50232`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 18 Jun 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 18 Jun 2025, 11:04 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: `18107f8a2df6bf1c6cac8d0713f757f866d5af51 to before 775871d4be0d75e219cca937af843a4a1b60489a` (git)
  - affected: `18107f8a2df6bf1c6cac8d0713f757f866d5af51 to before c3cee924bd855184d15bc4aa6088dcf8e2c1394c` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.13`
  - unaffected: `before 5.13` (semver)
  - unaffected: `5.15.60 to 5.15.*, inclusive` (semver)
  - unaffected: `6.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel on arm64 systems implementing FEAT_EPAN can panic because the swapper page tables do not set UXN, which denies access to the idmap. No attacker action is described; the flaw causes the kernel to crash. Affected versions are 5.13 and later up to 5.15.60 and 6.0, and users should upgrade to a patched kernel.

Written 16 Nov 2026.

## 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

No source has published a CVSS score for this record yet.

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

## Timeline

- 18 Jun 2025, 11:04 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-50232)
- 18 Jun 2025, 11:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50232)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/775871d4be0d75e219cca937af843a4a1b60489a>
- <https://git.kernel.org/stable/c/c3cee924bd855184d15bc4aa6088dcf8e2c1394c>

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-50232>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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