CVE-2026-53359

Aliases:SUSE-SU-2026:3376-1RHSA-2026:43847RHSA-2026:44003RHSA-2026:44004UBUNTU-CVE-2026-53359DEBIAN-CVE-2026-53359CGA-6c76-v4fc-94m9CGA-928j-8mhj-694r
Advisory lineage Upstream: 0 Downstream: 200
Modified
Published: 04 Jul 2026, 11:51
Last modified:17 Aug 2026, 04:50

Vulnerability Summary

Overall Risk (default)
medium
45/100
CVSS Score
8.8 HIGH
v3.1 (cve.org)
EPSS Score
0.96% LOW
1% probability 0.00%
KEV
Not listed
Ransomware
No reports
Public exploits
1 found
Dark Web
Not detected

Timeline

04 Jul 2026, 11:51
Published
Vulnerability first disclosed
17 Aug 2026, 04:50
Last Modified
Vulnerability information updated

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.

CVSS Metrics

  • v3.1•HIGH•Score: 8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
  • v3.1•HIGH•Score: 7.8CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS Trends

Current EPSS score: 0.96%• Percentile: 60%

Techniques & Countermeasures

  • CWE-416•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.

Affected Systems

  • chainguard•linux-gcp-6.18

    < 6.18.39-r0

  • chainguard•linux-gcp-6.18-bootc

    < 6.18.39-r0

  • debian•linux

    all | < 6.1.177-1 | < 6.12.95-1 | < 7.1.3-1

  • debian•linux-6.1

    < 6.1.177-1~deb11u1

  • ubuntu•linux

    all | < 3.13.0-215.266 | < 4.4.0-284.318 | < 4.15.0-254.266 | < 5.4.0-234.254 | < 5.15.0-187.197 | < 6.8.0-137.137 | all | < 7.0.0-29.29

  • ubuntu•linux-allwinner-5.19

    all

  • ubuntu•linux-aws

    all | < 4.4.0-1157.163 | < 4.4.0-1195.210 | < 4.15.0-1195.208 | < 5.4.0-1162.173 | < 5.15.0-1113.120 | < 6.8.0-1062.65 | all | < 7.0.0-1010.10

  • ubuntu•linux-aws-5.0

    all

  • ubuntu•linux-aws-5.11

    all

  • ubuntu•linux-aws-5.13

    all

  • ubuntu•linux-aws-5.15

    all | < 5.15.0-1114.121~20.04.1

  • ubuntu•linux-aws-5.19

    all

  • ubuntu•linux-aws-5.3

    all

  • ubuntu•linux-aws-5.4

    all | < 5.4.0-1162.173~18.04.1

  • ubuntu•linux-aws-5.8

    all

  • ubuntu•linux-aws-6.14

    all

  • ubuntu•linux-aws-6.17

    all

  • ubuntu•linux-aws-6.2

    all

  • ubuntu•linux-aws-6.5

    all

  • ubuntu•linux-aws-6.8

    all | < 6.8.0-1062.65~22.04.2

  • ubuntu•linux-aws-7.0

    all | < 7.0.0-1010.10~24.04.1

  • ubuntu•linux-aws-fips

    < 4.15.0-2133.139 | all | < 5.4.0-1163.174+fips1 | < 5.15.0-1113.120+fips1 | < 6.8.0-1062.65+fips1

  • ubuntu•linux-aws-hwe

    all | < 4.15.0-1195.208~16.04.1

  • ubuntu•linux-azure

    all | < 4.15.0-1205.220~14.04.1 | < 4.15.0-1205.220~16.04.1 | all | < 5.4.0-1167.173 | < 5.15.0-1118.127 | < 6.8.0-1064.72 | all | < 7.0.0-1011.11

  • ubuntu•linux-azure-4.15

    < 4.15.0-1205.220

  • ubuntu•linux-azure-5.11

    all

  • ubuntu•linux-azure-5.13

    all

  • ubuntu•linux-azure-5.15

    all | < 5.15.0-1119.128~20.04.1

  • ubuntu•linux-azure-5.19

    all

  • ubuntu•linux-azure-5.3

    all

  • ubuntu•linux-azure-5.4

    all | < 5.4.0-1167.173~18.04.1

  • ubuntu•linux-azure-5.8

    all

  • ubuntu•linux-azure-6.11

    all

  • ubuntu•linux-azure-6.14

    all

  • ubuntu•linux-azure-6.17

    < 6.17.0-1022.22

  • ubuntu•linux-azure-6.2

    all

  • ubuntu•linux-azure-6.5

    all

  • ubuntu•linux-azure-6.8

    < 6.8.0-1064.72~22.04.1

  • ubuntu•linux-azure-7.0

    all

  • ubuntu•linux-azure-edge

    all

  • ubuntu•linux-azure-fde

    all | < 5.15.0-1118.127 | < 6.8.0-1063.70 | all | < 7.0.0-1010.10

  • ubuntu•linux-azure-fde-5.15

    all | < 5.15.0-1118.127~20.04.1

  • ubuntu•linux-azure-fde-5.19

    all

  • ubuntu•linux-azure-fde-6.14

    all

  • ubuntu•linux-azure-fde-6.17

    all

  • ubuntu•linux-azure-fde-6.2

    all

  • ubuntu•linux-azure-fde-6.8

    < 6.8.0-1063.70~22.04.1

  • ubuntu•linux-azure-fips

    < 4.15.0-2113.119 | all | < 5.4.0-1167.173+fips1 | < 5.15.0-1118.127+fips1 | < 6.8.0-1064.72+fips1

  • ubuntu•linux-azure-nvidia

    all

  • ubuntu•linux-azure-nvidia-6.14

    all

Showing first 50 affected entries in server-rendered view.

References (68)