GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel virtio-crypto: unbounded device-reported result length over-reads guest kernel heap

UnscoredCVE-2026-80836Kernel, userspace & hypervisorcurated

Impact

The guest driver set the akcipher result length from the length the device reported, without clamping it to the destination buffer allocated for the original request. sg_copy_from_buffer() then copies that many bytes, so a backend reporting a larger length pushes adjacent guest kernel heap into the caller's scatterlist - an out-of-bounds read that surfaces kernel memory to whoever requested the operation. This is a host-to-guest trust boundary failure: a compromised or hostile device backend gets an information leak inside the guest kernel. Its practical reach is narrow, since virtio-crypto is rarely attached to GPU VMs; nodes that do not expose the device are unaffected.

Who can reach it

A malicious or compromised virtio-crypto backend (host-side device emulation) against a guest that has a virtio-crypto device attached and the driver loaded. Inside the guest, the leaked bytes land in the buffer of whichever process requested the akcipher operation; no guest privilege is required to be the recipient.

What to do

Apply the stable kernel fix (linked commits, which clamp the reported length to the requested destination length) to guest kernels and reboot them. The record names commits, not a fixed release. Where patching has to wait, stop exposing virtio-crypto devices to guests or keep the virtio_crypto module unloaded - conforming backends never report more than the requested length, so removing the device removes the exposure.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.