GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel vmw_pvrdma: double free on ucontext allocation error path

CVSS 7.8CVE-2026-46189Kernel, userspace & hypervisorcurated

Impact

A local user who can open the paravirtual RDMA device can force the ucontext allocation to fail and trigger a double free, because pvrdma_uar_free() is called both directly and again inside pvrdma_dealloc_ucontext(). Freeing the same UAR object twice corrupts kernel allocator state, which is the classic starting point for local privilege escalation on a shared node. This only matters on guests running under VMware with the paravirtual RDMA adapter attached - it is not the mlx5/ConnectX path most GPU fabrics use, so a bare-metal or non-VMware fleet is unaffected. Where it does apply, a tenant VM with RDMA verbs access can escalate inside the guest.

Who can reach it

Local user inside a VMware guest with access to the pvrdma verbs device (/dev/infiniband/uverbsN). Authentication as an ordinary local user is required; no remote or fabric-side path.

What to do

Take the stable kernel fix (commits linked in the record) or the Red Hat errata kernel for RHEL 8/9/10, then reboot each affected guest. If the fleet does not use VMware paravirtual RDMA, unbinding or not attaching the pvrdma adapter removes the exposure without a reboot. No fixed version string is stated beyond the referenced stable commits.

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.