PoC Monitor
← All CVEs
CVE-2026-53359published 4 Jul 2026 11:51 UTCData: JSON · API

Linux

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

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.

First public PoC 2.2 daysafter publication · 6 Jul 2026
Public PoCs44 on GitHub
CVSS8.8high · scored by CNA · CWE-416
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 2032a93d66fa282ba0f2ea9152eeff9511fa9a96, < 0b5e8ead71e683bcf6232db16234cf7e6d553a23
  • >= 2032a93d66fa282ba0f2ea9152eeff9511fa9a96, < b1337aae5e194324e4810d561764e7793f8b3864
  • >= 2032a93d66fa282ba0f2ea9152eeff9511fa9a96, < 9291654d69e08542de37755cebe4d5b02c3170d1
  • >= 2032a93d66fa282ba0f2ea9152eeff9511fa9a96, < 2ad3afa40ac6aa340dada122f9abfa46c0a6eb35
  • >= 2032a93d66fa282ba0f2ea9152eeff9511fa9a96, < 5e470998a23e4c3d89ed24e8172cb22747e61efa
  • >= 2032a93d66fa282ba0f2ea9152eeff9511fa9a96, < 1ae7d5a6db6c190ce183e3098ca0e0846e14d462
  • >= 2032a93d66fa282ba0f2ea9152eeff9511fa9a96, < 81ccda30b4e83d8f5cc4fd50503c44e3a33abfeb

Fixed in 0b5e8ead71e683bcf6232db16234cf7e6d553a23, b1337aae5e194324e4810d561764e7793f8b3864, 9291654d69e08542de37755cebe4d5b02c3170d1, 2ad3afa40ac6aa340dada122f9abfa46c0a6eb35, 5e470998a23e4c3d89ed24e8172cb22747e61efa, 1ae7d5a6db6c190ce183e3098ca0e0846e14d462, 81ccda30b4e83d8f5cc4fd50503c44e3a33abfeb

Linux Linux
  • 2.6.36

Fixed in 0, 5.15.222, 6.1.177, 6.6.144, 6.12.95, 6.18.38, 7.1.3, 7.2

Mitigation

Upgrade Linux to 0b5e8ead71e683bcf6232db16234cf7e6d553a23 or b1337aae5e194324e4810d561764e7793f8b3864 or 9291654d69e08542de37755cebe4d5b02c3170d1 or 2ad3afa40ac6aa340dada122f9abfa46c0a6eb35 or 5e470998a23e4c3d89ed24e8172cb22747e61efa or 1ae7d5a6db6c190ce183e3098ca0e0846e14d462 or 81ccda30b4e83d8f5cc4fd50503c44e3a33abfeb or later.

Upgrade Linux to 0 or 5.15.222 or 6.1.177 or 6.6.144 or 6.12.95 or 6.18.38 or 7.1.3 or 7.2 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published4 Jul 2026 · t = 0First public PoC6 Jul 2026 · t+2.2d

First public PoC 2.2 days after publication; not in CISA KEV. First PoC: V4bel/Januscape (created 6 Jul 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

4 PoCs · 2 pending · 2 informational · 1 not a PoC · 1 suspicious or fake

PoCs 4
RepositoryCreatedStarsAssessment
V4bel/Januscape 6 Jul 2026 +2.2 d 593 PoC via PoC Index
0xBlackash/CVE-2026-53359 7 Jul 2026 +2.8 d 4 PoC via PoC Index
0xredash/CVE-2026-53359 7 Jul 2026 +2.8 d 4 PoC via PoC Index
ashrafzaryouh/CVE-2026-53359 7 Jul 2026 +2.8 d 4 PoC via PoC Index
Pending 2
RepositoryCreatedStarsAssessment
Aoripus-LTD/Januscape-Hotfix 7 Jul 2026 +2.9 d 6 Pending · mkdir /quarantine/Aoripus-LTD__Januscape-Hotfix-10fca1afeec1: permission denied
suominen/januscape 8 Jul 2026 +3.9 d 0 Pending
Informational 2
RepositoryCreatedStarsAssessment
chuzhongyun/CVE-2026-53359-Kernel-Fix 7 Jul 2026 +3.4 d 2 Informational · detection
Flags · score 25
  • contains archives (archives/elrepo-release-8.el8.elrepo.noarch.rpm)

Below the suspicion threshold (50); does not change the assessment.

ndouglas-cloudsmith/CVE-2026-53359 15 Jul 2026 +11 d 0 Informational · write-up
Not a PoC 1
RepositoryCreatedStarsAssessment
HackSpeak/CVE-2026-64561 8 Aug 2026 +35 d 2 Not a PoC · unrelated
Flags · score 30
  • owner account created less than 7 days before the repo

Below the suspicion threshold (50); does not change the assessment.

Suspicious or fake 1
RepositoryCreatedStarsAssessment
HORKimhab/CVE-2026-53359 7 Jul 2026 +2.7 d 0 Fake

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.

Other public exploits

Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.
SourceTitlePublishedFound by us
CVE record (tagged exploit)https://github.com/V4bel/Januscape/blob/main/assets/write-up.mdunknown14 Nov 2026