cbcvebase.
CVE-2026-53359
published 2026-07-04

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…

PriorityP349high8.8CVSS 3.1
AVLACLPRLUINSCCHIHAH
EPSS
0.91%
56.3th percentile
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.

Affected

13 ranges
VendorProductVersion rangeFixed in
linuxlinux
linuxlinux>= 2032a93d66fa282ba0f2ea9152eeff9511fa9a96 < b1337aae5e194324e4810d561764e7793f8b3864b1337aae5e194324e4810d561764e7793f8b3864
linuxlinux>= 2032a93d66fa282ba0f2ea9152eeff9511fa9a96 < 9291654d69e08542de37755cebe4d5b02c3170d19291654d69e08542de37755cebe4d5b02c3170d1
linuxlinux>= 2032a93d66fa282ba0f2ea9152eeff9511fa9a96 < 2ad3afa40ac6aa340dada122f9abfa46c0a6eb352ad3afa40ac6aa340dada122f9abfa46c0a6eb35
linuxlinux>= 2032a93d66fa282ba0f2ea9152eeff9511fa9a96 < 5e470998a23e4c3d89ed24e8172cb22747e61efa5e470998a23e4c3d89ed24e8172cb22747e61efa
linuxlinux>= 2032a93d66fa282ba0f2ea9152eeff9511fa9a96 < 1ae7d5a6db6c190ce183e3098ca0e0846e14d4621ae7d5a6db6c190ce183e3098ca0e0846e14d462
linuxlinux>= 2032a93d66fa282ba0f2ea9152eeff9511fa9a96 < 81ccda30b4e83d8f5cc4fd50503c44e3a33abfeb81ccda30b4e83d8f5cc4fd50503c44e3a33abfeb
linuxlinux_kernel
linuxlinux_kernel>= 2.6.36 < 6.1.1776.1.177
linuxlinux_kernel>= 6.13 < 6.18.386.18.38
linuxlinux_kernel>= 6.19 < 7.1.37.1.3
linuxlinux_kernel>= 6.2 < 6.6.1446.6.144
linuxlinux_kernel>= 6.7 < 6.12.956.12.95

CVSS provenance

nvdv3.18.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
vendor_redhat7.0HIGH
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.