x86/tdx: Fix "in-kernel MMIO" check
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 18ecd5b74682839e7cdafb7cd1ec106df7baa18c, Kernel 25703a3c980e21548774eea8c8a87a75c5c8f58c, Kernel 4c0c5dcb5471de5fc8f0a1c4980e5815339e1cee and 2 more.
In the Linux kernel, the following vulnerability has been resolved: x86/tdx: Fix "in-kernel MMIO" check TDX only supports kernel-initiated MMIO operations. The handle_mmio() function checks if the #VE exception occurred in the kernel and rejects the operation if it did not. However, userspace can deceive the kernel into performing MMIO on its behalf. For example, if userspace can point a syscall to an MMIO address, syscall does get_user() or put_user() on it, triggering MMIO #VE. The kernel will treat the #VE as in-kernel MMIO. Ensure that the target MMIO address is within the kernel before decoding instruction.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.19, >=31d58c4e557d46fa7f8557714250fb6f89c941ae <18ecd5b74682839e7cdafb7cd1ec106df7baa18c, >=31d58c4e557d46fa7f8557714250fb6f89c941ae <25703a3c980e21548774eea8c8a87a75c5c8f58c, >=31d58c4e557d46fa7f8557714250fb6f89c941ae <4c0c5dcb5471de5fc8f0a1c4980e5815339e1cee, >=31d58c4e557d46fa7f8557714250fb6f89c941ae <bca2e29f7e26ce7c3522f8b324c0bd85612f68e3, >=31d58c4e557d46fa7f8557714250fb6f89c941ae <d4fc4d01471528da8a9797a065982e05090e1d81 | 18ecd5b74682839e7cdafb7cd1ec106df7baa18c, 25703a3c980e21548774eea8c8a87a75c5c8f58c, 4c0c5dcb5471de5fc8f0a1c4980e5815339e1cee, bca2e29f7e26ce7c3522f8b324c0bd85612f68e3, d4fc4d01471528da8a9797a065982e05090e1d81 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket