CVE-2026-46189: RDMA/vmw_pvrdma: Fix double free on pvrdma_alloc_ucontext() error path
In the Linux kernel, the following vulnerability has been resolved:
RDMA/vmw_pvrdma: Fix double free on pvrdma_alloc_ucontext() error path
Sashiko points out that pvrdma_uar_free() is already called within
pvrdma_dealloc_ucontext(), so calling it before triggers a double free.
Security readout for executives and security teams
Plain-English summary
A double-free bug in the Linux VMware paravirtual RDMA driver can corrupt kernel memory when user-context allocation fails. A local, low-privileged user may be able to trigger serious confidentiality, integrity, or availability consequences, although exploitation requires a specific driver path and high complexity.
Executive priority
Prioritize affected multi-user or shared-workload VMware systems where paravirtual RDMA is enabled. Treat internet-facing status alone as a poor exposure indicator because attack access is local. Patch through normal expedited kernel maintenance, with faster handling where untrusted users or tenants can access the driver.
Technical view
The pvrdma_alloc_ucontext() error path calls pvrdma_uar_free() before pvrdma_dealloc_ucontext(), which already performs that cleanup. The duplicate release creates a CWE-763 double free. CVSS 3.1 is 7.0: local access, low privileges, high attack complexity, no user interaction, unchanged scope, and high potential impact across confidentiality, integrity, and availability.
Likely exposure
Exposure is most likely on affected Linux systems using the vmw_pvrdma VMware paravirtual RDMA driver and permitting untrusted local users to reach its user-context allocation path. Systems without that driver or RDMA configuration are less likely exposed. The supplied version data is ambiguous, so validate exact distribution builds against vendor advisories.
Exploitation context
The supplied record is not in KEV and provides no evidence of active exploitation or a public exploit. Exploitation is locally initiated, requires low privileges, and is rated high complexity. Successful triggering also appears dependent on reaching a particular allocation failure path.
Researcher notes
The root cause is duplicate cleanup on an allocation error path, not ordinary successful operation. The source bundle supplies eight upstream stable commits and multiple Red Hat advisories, indicating fixes across maintained branches. Exact vulnerable-to-fixed version boundaries cannot be reconstructed confidently from the supplied version list alone.
Mitigation direction
Install the vendor-provided fixed kernel package applicable to the system and reboot into it.
Match distribution kernels against the listed Red Hat advisories or upstream stable fix commits.
If patching is delayed, consult the distribution vendor for supported temporary mitigations.
Reduce unnecessary local-account and workload access to systems exposing paravirtual RDMA.
Validation and detection
Inventory running kernel versions and identify systems using the vmw_pvrdma driver.
Determine whether VMware paravirtual RDMA is configured and accessible to untrusted local users.
Compare each distribution kernel build with its applicable vendor advisory and fixed package.
After updating, reboot and verify the running kernel is the intended fixed build.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-763: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
1ADP providers
23Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-763 · source CWE mapping
Release of Invalid Pointer or Reference
Release of Invalid Pointer or Reference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.