GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel mlx5 vDPA: memory-region key creation reads past the firmware command buffer

CVE-2026-74712Kernel, userspace & hypervisorcurated

Impact

create_direct_keys() sizes the input length from the whole out+in+mtt structure but hands cmd_exec a pointer to the 'in' field only, so mlx5_copy_to_msg() reads sizeof(out) bytes beyond the allocation - CI caught a 272-byte read 16 bytes past a 4384-byte region. The stale heap bytes are copied into a ConnectX firmware command; on a KASAN or hardened kernel the same access is fatal to the host. This is the mlx5 vDPA path used to give VMs accelerated networking on ConnectX NICs, so it is exercised by ordinary guest lifecycle operations on the shared fabric NIC rather than by an unusual configuration. The record does not establish attacker-controlled content or escalation.

Who can reach it

Host-side path exercised when a guest's mlx5 vDPA device creates its memory-region keys - reached by starting or reconfiguring a VM on a ConnectX-backed vDPA interface. No credentials beyond the ability to boot such a VM; hosts not running mlx5_vdpa are unaffected.

What to do

Update to a stable kernel with the fix. mlx5_vdpa is in use while guests hold vDPA interfaces, so in practice this means draining the VMs off the node and rebooting rather than reloading the module under load. No vendor advisory beyond the kernel commits is present in the record.

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.