Skip to main content
Public proof of conceptFix available

CVE-2026-53359

A public proof of concept exists; no exploitation attested.

  • Published2026-07-04
  • Fixed in7.1.3 · 6.18.38 · 6.12.95 · 6.6.144 · 6.1.177
  • WeaknessCWE-416

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Fix shadow paging use-after-free due to unexpected role Commit 0cb2af2ea66ad ("KVM: x86: Fix shadow paging use-after-free due to unexpected GFN") fixed a shadow paging mismatch between stored and computed GFNs; the bug could be triggered by changing a PDE mapping from outside the guest, and then deleting a memslot. The rmap_remove() call would miss entries created after the PDE change because the GFN of the leaf SPTE does not match the GFN of the struct kvm_mmu_page. A similar hole however remains if the modified PDE points to a non-leaf page. In this case the gfn can be made to match, but the role does not match: the original large 2MB page creates a kvm_mmu_page with direct=1, while the new 4KB needs a kvm_mmu_page with direct=0. However, kvm_mmu_get_child_sp() does not compare the role, and therefore reuses the page. The next step is installing a leaf (4KB) SPTE on the new path which records an rmap entry under the gfn resolved by the walk. But when that child is zapped its parent kvm_mmu_page has direct=1 and kvm_mmu_page_get_gfn() computes the gfn for the 4KB page as sp->gfn + index instead of using sp->shadowed_translation[] (or sp->gfns[] in older kernels). It therefore fails to remove the recorded entry. When the memslot is dropped the shadow page is freed but the rmap entry survives, as in the scenario that was already fixed. Code that later walks that gfn (dirty logging, MMU notifier invalidation, and so on) dereferences an sptep that lies in the freed page, causing the use-after-free.

Timeline

dates in UTC
  1. 2026-07-0412:17CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-53359?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-53359?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Linux linux kernel
BranchAffectedFixed in
7.1≥ 6.19, < 7.1.37.1.3
6.x≥ 6.13, < 6.18.386.18.38
6.x≥ 6.7, < 6.12.956.12.95
6.x≥ 6.2, < 6.6.1446.6.144
6.1≥ 2.6.36, < 6.1.1776.1.177

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • kernelAlmaLinux:10all versions · fixed in 6.12.0-211.32.1.el10_2and 74 other packages
  • kernelAlmaLinux:9all versions · fixed in 5.14.0-687.24.1.el9_8and 73 other packages

Vendor advisories

  • CVE-2026-53359 Red Hat Product Security2,144 products fixed · 28 known affected

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

    bpftool as a component of Red Hat Enterprise Linux 7 · kernel as a component of Red Hat Enterprise Linux 7 · kernel-abi-whitelists as a component of Red Hat Enterprise Linux 7 · +25 more

  • RHSA-2026:54187 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.13.70 bug fix and security update

  • RHSA-2026:54205 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.12.96 bug fix and security update

  • RHSA-2026:43252 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.14.70 bug fix and security update

  • RHSA-2026:49033 Red Hat Product Security50 products fixed

    Red Hat Security Advisory: kernel security update

  • RHSA-2026:44230 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.18.50 bug fix and security update

21 more advisories

Full record on NVD

Fix

  1. Update Linux linux kernel to 7.1.3 · 6.18.38 · 6.12.95 · 6.6.144 · 6.1.177
  2. Vendor fix Red Hat Product Security RHSA-2026:54187 · 1 productFor OpenShift Container Platform 4.13 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
  3. Vendor fix Red Hat Product Security RHSA-2026:54205 · 1 productFor OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
  4. Vendor fix Red Hat Product Security RHSA-2026:43252 · 4 productsFor OpenShift Container Platform 4.14 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
  5. Vendor fix Red Hat Product Security RHSA-2026:49033 · 50 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fu…
  6. Vendor fix Red Hat Product Security RHSA-2026:44230 · 4 productsFor OpenShift Container Platform 4.18 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
  7. Vendor fix Red Hat Product Security RHSA-2026:44231 · 4 productsFor OpenShift Container Platform 4.19 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
7 repositories, unverifiedHORKimhab/CVE-2026-533590xBlackash/CVE-2026-53359Aoripus-LTD/Januscape-Hotfixchuzhongyun/CVE-2026-53359-Kernel-Fixsuominen/januscape
PoC-in-GitHub

Sources

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Published
2026-07-04
Last Modified
2026-10-03
NVD status
Modified

Frequently asked questions

What is CVE-2026-53359?

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Fix shadow paging use-after-free due to unexpected role Commit 0cb2af2ea66ad ("KVM: x86: Fix shadow paging use-after-free due to unexpected GFN") fixed a shadow paging mismatch between stored and computed GFNs; the bug could be triggered by changing a PDE mapping from outside the guest, and then deleting a memslot. The rmap_remove() call would miss entries created after the PDE change because the GFN of the leaf SPTE does not match the GFN of the struct kvm_mmu_page. A similar hole however remains if the modified PDE points to a non-leaf page. In this case the gfn can be made to match, but the role does not match: the original large 2MB page creates a kvm_mmu_page with direct=1, while the new 4KB needs a kvm_mmu_page with direct=0. However, kvm_mmu_get_child_sp() does not compare the role, and therefore reuses the page. The next step is installing a leaf (4KB) SPTE on the new path which records an rmap entry under the gfn resolved by the walk. But when that child is zapped its parent kvm_mmu_page has direct=1 and kvm_mmu_page_get_gfn() computes the gfn for the 4KB page as sp->gfn + index instead of using sp->shadowed_translation[] (or sp->gfns[] in older kernels). It therefore fails to remove the recorded entry. When the memslot is dropped the shadow page is freed but the rmap entry survives, as in the scenario that was already fixed. Code that later walks that gfn (dirty logging, MMU notifier invalidation, and so on) dereferences an sptep that lies in the freed page, causing the use-after-free.

Is CVE-2026-53359 actively exploited?

A proof-of-concept exploit exists for CVE-2026-53359, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2026-53359?

CVE-2026-53359 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database