KVM: x86: Request event processing for exception VM-Exits
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e663aa0755a11f13e45ebe65a0c37d47f5529560, Kernel 6513f7be321ea273ad19ceb08afeac2b93ea28dd, Kernel 88b23a2e8286b7016c3b58dc10093cf28c22aa3d and 4 more.
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Request event processing for exception VM-Exits Request event processing whenever kvm_queue_exception_vmexit() queues an exception VM-Exit. Most callers reach the helper through kvm_multiple_exception(), which already sets KVM_REQ_EVENT, but nested asynchronous page faults call it directly. Without another event request, vcpu_enter_guest() skips kvm_check_and_inject_events() and re-enters L2. A subsequent VM-Exit can clear the pending exception while reconstructing vectoring state, losing the synthetic #PF VM-Exit. The APF reason remains PAGE_NOT_PRESENT and a later regular #PF can consume the stale value. Setting KVM_REQ_EVENT in the common helper ensures that L1 receives the queued VM-Exit before KVM re-enters L2.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=7709aba8f71613ae5d18d8c00adb54948e6bedb3 <e663aa0755a11f13e45ebe65a0c37d47f5529560, >=7709aba8f71613ae5d18d8c00adb54948e6bedb3 <6513f7be321ea273ad19ceb08afeac2b93ea28dd, >=7709aba8f71613ae5d18d8c00adb54948e6bedb3 <88b23a2e8286b7016c3b58dc10093cf28c22aa3d, >=7709aba8f71613ae5d18d8c00adb54948e6bedb3 <a92a07205e010029796b35924655aebb903b2e7c, =6.1 | e663aa0755a11f13e45ebe65a0c37d47f5529560, 6513f7be321ea273ad19ceb08afeac2b93ea28dd, 88b23a2e8286b7016c3b58dc10093cf28c22aa3d, a92a07205e010029796b35924655aebb903b2e7c |
| linux-kernel: Kernel | >=6.13.0 <6.18.61, >=6.19.0 <7.3.2, >=6.1.0 <6.12.117 | 6.18.61, 7.3.2, 6.12.117 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket