{"id":"AZL-115064","summary":"CVE-2026-99544 affecting package kernel 6.6.161.1-1","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nDrivers: hv: vmbus: Bounds check the shared ring buffer indices\n\nIn a CoCo VM the host is untrusted. Since the VMBus ring buffer read and\nwrite indices live in shared memory, the guest has to treat both as\npotentially malicious.\n\nhv_ringbuffer_write() copies into the ring at write_index with no bounds\nchecking, so the host can make the guest write packet data at any offset\nup to 4 GiB past the start of the ring buffer. read_index matters too:\nthe available space derived from both indices is the only bound on how\nmuch is copied, and an out-of-range index can make it far larger than\nthe ring.\n\nThe fix is to validate both indices before use and to use the validated\nsnapshot instead of re-accessing. For invalid indices,\nhv_ringbuffer_write() logs and returns -EIO.\n\nOne re-read of write_index is left unchecked in this patch:\nhv_get_ring_bufferindices() fetches it again for the prev_indices\ntrailer. The value is only returned to the host and is not used as an\noffset or length for indexing. Since this is not a security issue, it is\naddressed later in the series.\n\nOpen-coding the bytes available arithmetic keeps the fix free of\nprerequisites; a later patch refactors it into a helper function.","modified":"2026-11-20T14:17:30.850758449Z","published":"2026-11-19T15:18:10Z","upstream":["CVE-2026-99544"],"references":[{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99544"}],"affected":[{"package":{"name":"kernel","ecosystem":"Azure Linux:3","purl":"pkg:rpm/azure-linux/kernel"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"6.6.161.1-1"}]}],"database_specific":{"source":"https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-115064.json"}}],"schema_version":"1.9.2"}