Linux kernel (drivers/vfio/pci/mlx5): Migration and dirty-tracking state flags for an mlx5 VF were packed into shared

CVSS 5.9CVE-2026-64472Firmware, BMC & network fabriccurated

Impact

Migration and dirty-tracking state flags for an mlx5 VF were packed into shared bitfields updated non-atomically from concurrent paths, including a reset on one device reaching across to another. A lost update means the driver's view of deferred_reset, dirty-logging active, or error state diverges from reality - a passthrough NIC can be treated as reset when it was not, or dirty-page logging can be believed active when it is off, which silently corrupts a migrated tenant's memory.

Who can reach it

Driven by tenant-visible actions on an mlx5 SR-IOV VF bound to mlx5-vfio-pci: a tenant issuing device resets or migration state changes through /dev/vfio/* while the operator's dirty-tracking or VF event handling runs concurrently. Conditional on Mellanox/NVIDIA ConnectX VFs with the mlx5 vfio variant driver - which is the standard configuration for SR-IOV NIC passthrough in GPU clouds.

What to do

Update to a stable kernel carrying commits 1dd99b8f / f1db80a6. Interim: bind VFs to plain vfio-pci where live migration and dirty tracking are not needed, and serialize tenant-initiated resets against migration operations in the VMM.

References

https://git.kernel.org/stable/c/1dd99b8f4e143592e12e5a77e7b538bc698116cb https://git.kernel.org/stable/c/f1db80a67da928a92ba460ede1be52d8941f46be https://nvd.nist.gov/vuln/detail/CVE-2026-64472

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.