{"api_version":"1","generated_at":"2026-11-20T19:00:10+00:00","cve":"CVE-2026-99544","urls":{"html":"https://cve.report/CVE-2026-99544","api":"https://cve.report/api/cve/CVE-2026-99544.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99544","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99544"},"summary":{"title":"Drivers: hv: vmbus: Bounds check the shared ring buffer indices","description":"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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-19 15:18:10","updated_at":"2026-11-19 15:18:10"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/1611ce4dc6cbace75f27db6a559af8d391a06118","name":"https://git.kernel.org/stable/c/1611ce4dc6cbace75f27db6a559af8d391a06118","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/cdb9126a79b608b4331dfdc03beb05be8d2563be","name":"https://git.kernel.org/stable/c/cdb9126a79b608b4331dfdc03beb05be8d2563be","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f204bb7c5d10482067e095af567c391bc88ecb44","name":"https://git.kernel.org/stable/c/f204bb7c5d10482067e095af567c391bc88ecb44","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/1d287c17cc5bfd6386fe0770999be410b248d021","name":"https://git.kernel.org/stable/c/1d287c17cc5bfd6386fe0770999be410b248d021","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99544","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99544","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3e7ee4902fe6996048f03433dd111426db3cfa92 cdb9126a79b608b4331dfdc03beb05be8d2563be git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3e7ee4902fe6996048f03433dd111426db3cfa92 f204bb7c5d10482067e095af567c391bc88ecb44 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3e7ee4902fe6996048f03433dd111426db3cfa92 1611ce4dc6cbace75f27db6a559af8d391a06118 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3e7ee4902fe6996048f03433dd111426db3cfa92 1d287c17cc5bfd6386fe0770999be410b248d021 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2.6.32","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 2.6.32 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.117 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.61 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3.2 7.3.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.4-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/hv/ring_buffer.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"cdb9126a79b608b4331dfdc03beb05be8d2563be","status":"affected","version":"3e7ee4902fe6996048f03433dd111426db3cfa92","versionType":"git"},{"lessThan":"f204bb7c5d10482067e095af567c391bc88ecb44","status":"affected","version":"3e7ee4902fe6996048f03433dd111426db3cfa92","versionType":"git"},{"lessThan":"1611ce4dc6cbace75f27db6a559af8d391a06118","status":"affected","version":"3e7ee4902fe6996048f03433dd111426db3cfa92","versionType":"git"},{"lessThan":"1d287c17cc5bfd6386fe0770999be410b248d021","status":"affected","version":"3e7ee4902fe6996048f03433dd111426db3cfa92","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/hv/ring_buffer.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"2.6.32"},{"lessThan":"2.6.32","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.117","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.61","versionType":"semver"},{"lessThanOrEqual":"7.3.*","status":"unaffected","version":"7.3.2","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.4-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.117","versionStartIncluding":"2.6.32","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.61","versionStartIncluding":"2.6.32","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.2","versionStartIncluding":"2.6.32","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc1","versionStartIncluding":"2.6.32","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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."}],"providerMetadata":{"dateUpdated":"2026-11-19T14:45:02.316Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/cdb9126a79b608b4331dfdc03beb05be8d2563be"},{"url":"https://git.kernel.org/stable/c/f204bb7c5d10482067e095af567c391bc88ecb44"},{"url":"https://git.kernel.org/stable/c/1611ce4dc6cbace75f27db6a559af8d391a06118"},{"url":"https://git.kernel.org/stable/c/1d287c17cc5bfd6386fe0770999be410b248d021"}],"title":"Drivers: hv: vmbus: Bounds check the shared ring buffer indices","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99544","datePublished":"2026-11-19T14:45:02.316Z","dateReserved":"2026-09-25T10:25:14.421Z","dateUpdated":"2026-11-19T14:45:02.316Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-19 15:18:10","lastModifiedDate":"2026-11-19 15:18:10","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99544","Ordinal":"1","Title":"Drivers: hv: vmbus: Bounds check the shared ring buffer indices","CVE":"CVE-2026-99544","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99544","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"Drivers: hv: vmbus: Bounds check the shared ring buffer indices"}]}}}