GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel nvmet-rdma: short RDMA-CM connection request causes out-of-bounds read on the NVMe-oF target

UnscoredCVE-2026-99302Kernel, userspace & hypervisorcurated

Impact

The NVMe-oF RDMA target accepts RDMA-CM private data of any nonzero length and parses it as a full connect request. On the iWARP path, where the buffer is allocated at exactly the length the peer sent, a six-byte request makes the target read two bytes past the allocation. The record shows a KASAN slab-out-of-bounds read and does not describe any further corruption, so the established impact is a small kernel heap over-read on the storage target before any NVMe authentication. Storage servers that export NVMe namespaces over RDMA to GPU nodes are the affected hosts.

Who can reach it

Anyone who can reach the NVMe-oF RDMA listener on the storage fabric, before any authentication. The demonstrated path is iWARP (including soft-iWARP/siw). Hosts that do not run the nvmet-rdma target are not affected.

What to do

Install a kernel with the stable fix on NVMe-oF target hosts and reboot them, which means failing over or taking down the namespaces they export. Restricting who can reach the target's RDMA ports reduces exposure until then.

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.