KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e27fc915c8f575ab5630e27d97465c2077d4b9d1, Kernel 2e9b8c79ae6c1dcf650ea288cf8fc69ee5241dd9, Kernel 5d06e2f861d61a03481348378fdf9cc3e68bff47 and 4 more.
In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded Leave control.erap_ctl and control.clean as-is in the VMCS if VMRUN fails, because as per AMD: there's no explicit architectural guarantee about the behavior in the presence of VMRUN failures. So the best thing to do would be to assume that if VMRUN fails, the actions requested in the control fields may not have been performed.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=8d28fec406e4d5ce6c109fe12699976e72e9748e <e27fc915c8f575ab5630e27d97465c2077d4b9d1, >=8d28fec406e4d5ce6c109fe12699976e72e9748e <2e9b8c79ae6c1dcf650ea288cf8fc69ee5241dd9, >=8d28fec406e4d5ce6c109fe12699976e72e9748e <5d06e2f861d61a03481348378fdf9cc3e68bff47, >=8d28fec406e4d5ce6c109fe12699976e72e9748e <8676b29d186fcb5c1251d8152fc91d19421e5600, =2.6.38 | e27fc915c8f575ab5630e27d97465c2077d4b9d1, 2e9b8c79ae6c1dcf650ea288cf8fc69ee5241dd9, 5d06e2f861d61a03481348378fdf9cc3e68bff47, 8676b29d186fcb5c1251d8152fc91d19421e5600 |
| linux-kernel: Kernel | >=6.13.0 <6.18.61, >=6.19.0 <7.2.10, >=2.6.38 <6.12.117 | 6.18.61, 7.2.10, 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