CVE-2026-53345: KVM: Don't WARN if memory is dirtied without a vCPU when the VM is dying
Vulnerability summary
CVE-2026-53345 is a medium (CVSS 5.5) vulnerability in linux. EPSS estimates a 0.12% chance of exploitation in the next 30 days, higher than 1.9% of scored vulnerabilities.
Not severe (CVSS 5.5, local access); no exploitation reported by the 5 checked sources
Source freshness unavailable
How is this decided?Advisory lineage
Upstream 0 · Downstream 34 · Related 32Timeline
- 01-07-2026PublishedVulnerability first disclosed.
- 06-11-2026Last modifiedVulnerability information updated.
Description
In the Linux kernel, the following vulnerability has been resolved: KVM: Don't WARN if memory is dirtied without a vCPU when the VM is dying When marking a page dirty, complain about not having a running/loaded vCPU if and only if the VM is still alive, i.e. its refcount is non-zero. This will allow fixing a memory leak for x86 SEV-ES guests without hitting what is effectively a false positive on the WARN. For some SEV-ES VM-Exits, KVM keeps a writable mapping of a guest page across an exit to userspace, and typically unmaps the page on the next KVM_RUN. But if userspace never calls KVM_RUN after such an exit, then KVM needs to unmap the page when the vCPU is destroyed, which in turn triggers the WARN about not having a running vCPU. Alternatively, SEV-ES could temporarily load the vCPU to suppress the WARN, as is done in nested_vmx_free_vcpu() (but for completely unrelated reasons; suppressing WARN from nested_put_vmcs12_pages() is pure happenstance). But loading a vCPU during destruction is gross (ideally nVMX code would be cleaned up), risks complicating the SEV-ES code (KVM would need to ensure the temporarily load()+put() only runs when the vCPU isn't already loaded), and is ultimately pointless. The motivation for the WARN is to guard against KVM dirtying guest memory without pushing the corresponding GFN to the active vCPU's dirty ring, e.g. to ensure userspace doesn't miss a dirty page. But for the VM's refcount to reach zero, there can't be _any_ userspace mappings to the dirty ring, as mapping the dirty ring requires doing mmap() on the vCPU FD. I.e. if userspace had a valid mapping for the dirty ring, then the vCPU file and thus the owning VM would still be alive. And so since userspace can't possibly reach the dirty ring, whether or not KVM technically "misses" a push to the dirty ring is irrelevant.
CVSS metrics
4 scores · 3 sources · 2 versions- OSV · UbuntuEcosystem advisory · calculated5.5MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- OSV · DebianEcosystem advisory · calculated5.5MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS trend
Probability
0.12%
Chance of exploitation in the next 30 days
Percentile
2%
Versus all other CVEs
30-day change
No change 0.00 pp
From 0.12% on 21-10-2026
Known exploited
Compare KEV catalogsNot in the CISA KEV catalog.
Not in the ENISA CNW catalog.
Not in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeAffected systems
Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.
Ubuntu169 products
- linuxAll versions (No fix recorded) | < 6.8.0-146.146 | < 7.0.0-31.31
- linux-allwinner-5.19All versions (No fix recorded)
- linux-awsAll versions (No fix recorded) | < 6.8.0-1066.69 | < 7.0.0-1012.12
- linux-aws-5.0All versions (No fix recorded)
- linux-aws-5.11All versions (No fix recorded)
Linux2 products
- linux≥ 2efd61a608b0039911924d2e5d7028eb37496e85, < 21b880f040bd0e8b50ff30c5a40db7bf3384ff48 | ≥ 2efd61a608b0039911924d2e5d7028eb37496e85, < 033d39e41fc30f484f4e4f37fb4cd76b12cbb18e | ≥ 2efd61a608b0039911924d2e5d7028eb37496e85, < 66a8e7ddd901023c89a2733494d827eca3f9c1b0 | ≥ 2efd61a608b0039911924d2e5d7028eb37496e85, < 343e95c8ecc40e0738975ef4ee24c0c35e800e6b | ≥ 2efd61a608b0039911924d2e5d7028eb37496e85, < 99d7d43784ae3235026581e9bf892c036e04c8e6 | ≥ 2efd61a608b0039911924d2e5d7028eb37496e85, < 8618004d3e897c0f1b71d9a9ab860461289bb89a | 5.17
- linux_kernel≥ 5.17, < 6.6.143 | ≥ 6.7, < 6.12.94 | ≥ 6.13, < 6.18.36 | ≥ 6.19, < 7.0.13 | 7.1:rc1 | 7.1:rc2 | 7.1:rc3 | 7.1:rc4 | 7.1:rc5 | 7.1:rc6
Debian1 product
- linuxAll versions (No fix recorded) | < 6.1.192-1 | < 6.12.94-1 | < 7.0.13-1
3 vendors · 172 products