CVE-2026-99544
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. hv_ringbuffer_write() copies into the ring at write_index 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. read_index 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, hv_ringbuffer_write() logs and returns -EIO. One re-read of write_index is left unchecked in this patch: hv_get_ring_bufferindices() fetches it again for the prev_indices 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.
Properties
- Severity
- CRITICAL
- Nvd fetched at
- 2026-11-22T12:30:49.958423+00:00
- Cvss score
- 9.3
- Cvss severity
- CRITICAL
- Epss score
- 0.00157
- Retrieved at
- 2026-11-22T12:32:29+00:00
- Last source
- FIRST EPSS
- Score
- 9.3
- Cvss version
- 3.1
- Cve id
- CVE-2026-99544
- Cvss vector
- CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- First seen by Signal
- 2026-11-19T15:26:52+00:00
- Name
- CVE-2026-99544
- Vector
- CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- Published at
- 2026-11-19T15:18:10.540
- Last modified
- 2026-11-22T11:16:55.837
- Epss percentile
- 0.04837
Related research
Explore deeper with Ninja Signal's threat intelligence graph