Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-46113

kernel: KVM: x86: Fix shadow paging use-after-free due to unexpected GFN

Overview

Published
28 May 2026
Modified
19 Oct 2026
High CVE
0 Registry packages
384 OS packages
14 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

8.8 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Weakness: CWE-416

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 245 fixes

Azure Linux 1 release · 1 package

fixed 1
kernel
Azure Linux fixes for CVE-2026-46113
ReleasePackageFixed in
3.0 kernel 0:6.6.141.1-1.azl3

Oracle Linux 2 releases · 2 packages

fixed 4
kernel bpftool
Oracle Linux fixes for CVE-2026-46113
ReleasePackageFixed in
8 kernel +18 4.18.0-553.143.1.el8_10
8 bpftool +13 5.15.0-323.211.3.3.el8uek
9 kernel +28 5.14.0-687.24.1.el9_8
9 bpftool +18 5.15.0-323.211.3.3.el9uek

Photon OS 1 release · 2 packages

fixed 2
bpftool linux-esx
Photon OS fixes for CVE-2026-46113
ReleasePackageFixed in
5.0 bpftool +7 6.1.175-1.ph5
5.0 linux-esx +2 6.1.177-1.ph5

Red Hat 2 releases · 3 packages

fixed 11 affected 1
bpftool kernel-rt kernel
Red Hat fixes for CVE-2026-46113
ReleasePackageFixed inAdvisory
8 bpftool +16 0:4.18.0-372.204.1.el8_6 RHSA-2026:49033
8 bpftool +16 0:4.18.0-477.154.1.el8_8 RHSA-2026:41229
8 bpftool +22 0:4.18.0-553.143.1.el8_10 RHSA-2026:39083
8 kernel-rt +11 0:4.18.0-553.143.1.rt7.484.el8_10 RHSA-2026:39082
9 kernel-rt +20 affected —
9 kernel +43 0:5.14.0-284.181.1.el9_2 RHSA-2026:40082

6 more rows

SUSE Linux Enterprise 6 releases · 29 packages

fixed 38
kgraft-patch-4-12-14-122-317-default kgraft-patch-4-12-14-122-290-default kgraft-patch-4-12-14-122-310-default cluster-md-kmp-default kernel-livepatch-5-14-21-150400-24-222-default kernel-livepatch-5-14-21-150400-24-219-default +23
SUSE Linux Enterprise fixes for CVE-2026-46113
ReleasePackageFixed inAdvisory
12.5 kgraft-patch-4-12-14-122-317-default 1-8.7.1 SUSE-SU-2026:2450-1
12.5 kgraft-patch-4-12-14-122-290-default 11-2.1 SUSE-SU-2026:3388-1
12.5 kgraft-patch-4-12-14-122-310-default 4-2.1 SUSE-SU-2026:3383-1
12.5 cluster-md-kmp-default +13 4.12.14-122.317.1 SUSE-SU-2026:2450-1
15.4 kernel-livepatch-5-14-21-150400-24-222-default 1-150400.9.3.1 SUSE-SU-2026:2383-1
15.4 kernel-livepatch-5-14-21-150400-24-219-default 3-150400.2.1 SUSE-SU-2026:3351-1

32 more rows

SUSE Linux Enterprise Micro 6 releases · 54 packages

fixed 91
kernel-rt kernel-default kernel-default-base kernel-devel-rt kernel-livepatch-6-4-0-38-rt kernel-livepatch-6-4-0-37-rt +48
SUSE Linux Enterprise Micro fixes for CVE-2026-46113
ReleasePackageFixed inAdvisory
5.3 kernel-rt +1 5.14.21-150400.15.170.1 SUSE-SU-2026:2331-1
5.3 kernel-default +2 5.14.21-150400.24.222.1 SUSE-SU-2026:2383-1
5.3 kernel-default-base 5.14.21-150400.24.222.1.150400.24.112.1 SUSE-SU-2026:2383-1
5.4 kernel-rt +1 5.14.21-150400.15.170.1 SUSE-SU-2026:2331-1
5.4 kernel-default +2 5.14.21-150400.24.222.1 SUSE-SU-2026:2383-1
5.4 kernel-default-base 5.14.21-150400.24.222.1.150400.24.112.1 SUSE-SU-2026:2383-1

85 more rows

alma 3 releases · 4 packages

fixed 4
kernel-abi-stablelists bpftool kernel-rt kernel
alma fixes for CVE-2026-46113
ReleasePackageFixed in
10 kernel-abi-stablelists +1 6.12.0-211.32.1.el10_2
8 bpftool +19 4.18.0-553.143.1.el8_10
8 kernel-rt +9 4.18.0-553.143.1.rt7.484.el8_10
9 kernel +40 5.14.0-687.24.1.el9_8

amazon linux 1 release · 4 packages

fixed 4
kernel-livepatch-6-1-175-219-357 bpftool bpftool6-12 bpftool6-18
amazon linux fixes for CVE-2026-46113
ReleasePackageFixed in
2023 kernel-livepatch-6-1-175-219-357 +2 1:1.0-0.amzn2023
2023 bpftool +16 1:6.1.175-219.357.amzn2023
2023 bpftool6-12 +16 1:6.12.88-119.157.amzn2023
2023 bpftool6-18 +16 1:6.18.30-61.116.amzn2023

debian 4 releases · 2 packages

affected 1 fixed 4
linux linux-6-1
debian fixes for CVE-2026-46113
ReleasePackageFixed in
11 linux affected
11 linux-6-1 6.1.176-1~deb11u1
12 linux 6.1.176-1
13 linux 6.12.88-1
14 linux 7.0.7-1

echo 1 release · 1 package

fixed 1
linux
echo fixes for CVE-2026-46113
ReleasePackageFixed in
linux 1

openSUSE 1 release · 1 package

fixed 1
kernel-devel
openSUSE fixes for CVE-2026-46113
ReleasePackageFixed inAdvisory
Tumbleweed kernel-devel +3 7.0.11-1.1 openSUSE-SU-2026:10954-1

openSUSE Leap 1 release · 2 packages

fixed 2
cluster-md-kmp-64kb kernel-default-base
openSUSE Leap fixes for CVE-2026-46113
ReleasePackageFixed inAdvisory
16.0 cluster-md-kmp-64kb +74 6.12.0-160000.37.1 openSUSE-SU-2026:21555-1
16.0 kernel-default-base 6.12.0-160000.37.1.160000.2.19 openSUSE-SU-2026:21555-1

rocky 2 releases · 1 package

fixed 2
kernel
rocky fixes for CVE-2026-46113
ReleasePackageFixed in
10 kernel +28 6.12.0-211.32.1.el10_2
9 kernel +27 5.14.0-687.24.1.el9_8

ubuntu 5 releases · 56 packages

affected 4 fixed 74
linux linux-nvidia-tegra-5-15 linux-ibm-5-15 linux-riscv-5-15 linux-intel-iotg-5-15 linux-oracle-5-15 +50
ubuntu fixes for CVE-2026-46113
ReleasePackageFixed in
18.04-ESM linux +12 affected
20.04-ESM linux +10 affected
20.04-ESM linux-nvidia-tegra-5-15 5.15.0-1070.72~20.04.1
20.04-ESM linux-ibm-5-15 5.15.0-1113.117~20.04.1
20.04-ESM linux-riscv-5-15 5.15.0-1113.117~20.04.2
20.04-ESM linux-intel-iotg-5-15 5.15.0-1114.120~20.04.1

72 more rows

References

Show all 66 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.