# KVM: x86/mmu: Treat NX as a valid SPTE bit for NPT

CVE record · `CVE-2022-50224`

- **Identifiers:** `CVE-2022-50224`
- **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:03 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: `b8e8c8303ff28c61046a4d0f6ea99aea609a7dc0 to before 6271f2854b9233702e236e576b885a876dde4889` (git)
  - affected: `b8e8c8303ff28c61046a4d0f6ea99aea609a7dc0 to before 6c6ab524cfae0799e55c82b2c1d61f1af0156f8d` (git)
  - affected: `a7ad7943b84fae87f5be18f05025c51ae103f732` (git)
  - affected: `bb16a6ba5d1ed79b40caea8d924e237f63205b7c` (git)
  - affected: `5219505fcbb640e273a0d51c19c38de0100ec5a9` (git)
  - affected: `78ffa84f00ff6b19f00c0e6dfe1870aba0db4025` (git)
  - affected: `4.9.202 to before 4.10` (semver)
  - affected: `4.14.154 to before 4.15` (semver)
  - affected: `4.19.84 to before 4.20` (semver)
  - affected: `5.3.11 to before 5.4` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.4`
  - unaffected: `before 5.4` (semver)
  - unaffected: `5.19.2 to 5.19.*, 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 KVM code on AMD hosts using NPT can trigger a kernel WARN when the NX huge page mitigation is enabled, because the NX bit is treated as a reserved SPTE bit. The source gives few details on attacker access or impact. Upgrade to Linux 5.19.2 or later in the 5.19 series, or to 6.0 or later.

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:03 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-50224)
- 18 Jun 2025, 11:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50224)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/6271f2854b9233702e236e576b885a876dde4889>
- <https://git.kernel.org/stable/c/6c6ab524cfae0799e55c82b2c1d61f1af0156f8d>

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

---

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