# CVE-2026-99544: Drivers: hv: vmbus: Bounds check the shared ring buffer indices

Status: published. Published: 2026-11-19. Updated: 2026-11-22.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 3e7ee4902fe6996048f03433dd111426db3cfa92; < cdb9126a79b608b4331dfdc03beb05be8d2563be (affected, git); ≥ 3e7ee4902fe6996048f03433dd111426db3cfa92; < f204bb7c5d10482067e095af567c391bc88ecb44 (affected, git); ≥ 3e7ee4902fe6996048f03433dd111426db3cfa92; < 1611ce4dc6cbace75f27db6a559af8d391a06118 (affected, git); ≥ 3e7ee4902fe6996048f03433dd111426db3cfa92; < 1d287c17cc5bfd6386fe0770999be410b248d021 (affected, git). Source: 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). Source: CNA: Linux

## Severity and prioritization

- CVSS 3.1: 9.3 (critical); CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H; source: CNA: Linux

- CVSS 3.1: 9.3 (critical); CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H; source: NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

- CISA KEV: No listing in collected sources

- EPSS: 0.16% as of 2026-11-21; percentile 4.84%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/cdb9126a79b608b4331dfdc03beb05be8d2563be (CNA: Linux)

- https://git.kernel.org/stable/c/f204bb7c5d10482067e095af567c391bc88ecb44 (CNA: Linux)

- https://git.kernel.org/stable/c/1611ce4dc6cbace75f27db6a559af8d391a06118 (CNA: Linux)

- https://git.kernel.org/stable/c/1d287c17cc5bfd6386fe0770999be410b248d021 (CNA: Linux)

- https://git.kernel.org/stable/c/1611ce4dc6cbace75f27db6a559af8d391a06118 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/1d287c17cc5bfd6386fe0770999be410b248d021 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/cdb9126a79b608b4331dfdc03beb05be8d2563be (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/f204bb7c5d10482067e095af567c391bc88ecb44 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99544; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99544; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99544; retrieved 2026-11-22; source updated Not reported

Revision: 1da6dc7d7dcfa3b0f3e7d1c7cfb9b5cdd6165be34d94a6e3b6a64e83062ae34b

Canonical: https://y2.dev/cve/CVE-2026-99544

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.