uio_hv_generic: Don't free decrypted memory
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
uio_hv_generic: Don't free decrypted memory
In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to handle these errors to avoid returning decrypted (shared) memory to the page allocator, which could lead to functional or security issues.
The VMBus device UIO driver could free decrypted/shared pages if set_memory_decrypted() fails. Check the decrypted field in the gpadl to decide whether to free the memory.
From the CVE record · Linux
In confidential computing (CoCo) VMs, the VMBus device UIO driver can return decrypted, shared memory to the page allocator if set_memory_decrypted() fails. An untrusted host can cause that failure, potentially leading to security or functional issues. The input does not specify authentication or user-interaction requirements.
Operators running Linux kernels with the VMBus device UIO driver in CoCo VMs should check their exposure; affected versions are not specified.