Skip to content

In the Linux kernel, the following vulnerability has been...

High severity Unreviewed Published May 28, 2026 to the GitHub Advisory Database • Updated Oct 15, 2026

Package

No package listed— Suggest a package

Affected versions

Unknown

Patched versions

Unknown

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.

References

Published by the National Vulnerability Database May 28, 2026
Published to the GitHub Advisory Database May 28, 2026
Last updated Oct 15, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(9th percentile)

Weaknesses

Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer. Learn more on MITRE.

CVE ID

CVE-2026-46113

GHSA ID

GHSA-gcf3-9g28-gv44

Source code

No known source code

Dependabot alerts are not supported on this advisory because it does not have a package from a supported ecosystem with an affected and fixed version.

Learn more about GitHub language support

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.