x86/tdx: Fix "in-kernel MMIO" check
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s x86/tdx MMIO handler can mistake userspace-triggered MMIO for kernel-initiated MMIO. A local userspace process can trigger this through a syscall that accesses an MMIO address, bypassing the check intended to reject such operations. No separate user interaction is described.
Engineers running Linux kernels with x86/tdx support should check their kernel versions against the vendor advisory; affected versions are not specified in the input.