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. 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.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 3e7ee4902fe6996048f03433dd111426db3cfa92; < cdb9126a79b608b4331dfdc03beb05be8d2563be (affected, git) ≥ 3e7ee4902fe6996048f03433dd111426db3cfa92; < f204bb7c5d10482067e095af567c391bc88ecb44 (affected, git) ≥ 3e7ee4902fe6996048f03433dd111426db3cfa92; < 1611ce4dc6cbace75f27db6a559af8d391a06118 (affected, git) ≥ 3e7ee4902fe6996048f03433dd111426db3cfa92; < 1d287c17cc5bfd6386fe0770999be410b248d021 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
2.6.32 (affected) ≥ 0; < 2.6.32 (unaffected, semver) ≥ 6.12.117; ≤ 6.12.* (unaffected, semver) ≥ 6.18.61; ≤ 6.18.* (unaffected, semver) ≥ 7.3.2; ≤ 7.3.* (unaffected, semver) ≥ 7.4-rc1; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 9.3 critical |
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | CNA: Linux |
| 3.1 / 9.3 critical |
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/cdb9126a79b608b4331dfdc03beb05be8d2563beCNA: Linux
- https://git.kernel.org/stable/c/f204bb7c5d10482067e095af567c391bc88ecb44CNA: Linux
- https://git.kernel.org/stable/c/1611ce4dc6cbace75f27db6a559af8d391a06118CNA: Linux
- https://git.kernel.org/stable/c/1d287c17cc5bfd6386fe0770999be410b248d021CNA: Linux
- https://git.kernel.org/stable/c/1611ce4dc6cbace75f27db6a559af8d391a06118416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/1d287c17cc5bfd6386fe0770999be410b248d021416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/cdb9126a79b608b4331dfdc03beb05be8d2563be416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/f204bb7c5d10482067e095af567c391bc88ecb44416baaa9-dc9f-4396-8d5f-8c081fb06d67
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.