CVE-2026-99544: Drivers: hv: vmbus: Bounds check the shared ring buffer indices
In the Linux kernel, the following vulnerability has been resolved:
Drivers: hv: vmbus: Bounds check the shared ring buffer indices
In a CoCo VM the host is untrusted. Since the VMBus ring buffer read and write indices live in shared memory, the guest has to treat both as potentially malicious.
hvringbufferwrite() copies into the ring at writeindex with no bounds checking, so the host can make the guest write packet data at any offset up to 4 GiB past the start of the ring buffer. readindex matters too: the available space derived from both indices is the only bound on how much is copied, and an out-of-range index can make it far larger than the ring.
The fix is to validate both indices before use and to use the validated snapshot instead of re-accessing. For invalid indices, hvringbufferwrite() logs and returns -EIO.
One re-read of writeindex is left unchecked in this patch: hvgetringbufferindices() fetches it again for the previndices trailer. The value is only returned to the host and is not used as an offset or length for indexing. Since this is not a security issue, it is addressed later in the series.
Open-coding the bytes available arithmetic keeps the fix free of prerequisites; a later patch refactors it into a helper function.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.117 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.61 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2 - Compensating control
Validate both shared ring buffer indices before use, and use the validated snapshot instead of re-reading write_index.