GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel NVMe: use-after-free on the admin request_queue during controller teardown

CVSS 7.8CVE-2025-68265Kernel, userspace & hypervisorcurated

Impact

Namespaces could keep stale references to a controller's admin request_queue after the controller was torn down, so an ioctl arriving during or after teardown dereferences freed memory (KASAN slab-use-after-free in blk_queue_enter). The practical outcome is a host crash or corruption on a storage hot-remove, controller reset or driver unload path; the CVSS vector claims confidentiality, integrity and availability impact from a local low-privileged position, but reaching it needs the NVMe passthrough ioctl path. On a GPU node this is an availability problem first: local NVMe holds model weights, datasets and container images, and a kernel oops takes the whole node and every tenant job on it down with no graceful drain.

Who can reach it

Local. Requires the ability to issue NVMe passthrough ioctls on a /dev/nvme* character device - on a normal fleet that is root or a user explicitly granted the device, not an ordinary tenant pod - racing a controller teardown or reset.

What to do

Pick up the fix from the stable kernel series (commits linked in the record) via your distribution's kernel update. There is no runtime mitigation other than avoiding NVMe passthrough ioctls around controller resets, so this is a kernel upgrade: drain the node and reboot it. Batch it with the next scheduled kernel maintenance rather than opening a window tonight - exposure is local and privileged.

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.