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
This is a Linux kernel memory-management flaw in the VMware paravirtual RDMA driver path. A local low-privileged user could potentially trigger serious confidentiality, integrity, and availability impact, but exploitation is rated high complexity and requires local access.
Executive priority
Treat as a high-priority kernel maintenance item, especially for multi-user Linux, virtualization, or workload-hosting environments. There is no supplied evidence of active exploitation, so prioritize patching through normal emergency kernel channels rather than incident response escalation.
Technical view
The resolved kernel issue is a double free in pvrdma_alloc_ucontext() error handling. The source says pvrdma_uar_free() is already called inside pvrdma_dealloc_ucontext(), so calling it before deallocation frees the same resource twice.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions or commit lineages with the RDMA/vmw_pvrdma code present. Systems without this driver path enabled or reachable by local users are likely lower exposure, but the bundle does not provide full distribution-specific scope beyond Linux and Red Hat references.
Exploitation context
The CVSS vector is local, high complexity, low privileges required, no user interaction, with high CIA impact. KEV is false, and the provided sources do not state active exploitation or public weaponization.
Researcher notes
Focus review on the pvrdma_alloc_ucontext() error path and resource ownership around pvrdma_uar_free() and pvrdma_dealloc_ucontext(). The bundle identifies CWE-1341 and multiple stable commits, but does not provide proof-of-concept details or distribution-level exploitability conditions.
Mitigation direction
Apply vendor kernel updates that include the referenced stable fixes.
Review Red Hat RHSA advisories if using affected Red Hat platforms.
Track distribution advisories for backported fixes, not only upstream version numbers.
If RDMA/vmw_pvrdma is unused, check vendor guidance for reducing exposure.
Validation and detection
Inventory Linux kernel versions across hosts and images.
Determine whether affected vmw_pvrdma/RDMA kernel code is present or enabled.
Confirm installed kernel packages map to fixed vendor advisories.
Verify the kernel includes the relevant upstream stable fix or backport.
Prioritize shared systems where untrusted local users have shell or workload access.
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-1341: 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
22Source 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-1341 · source CWE mapping
Multiple Releases of Same Resource or Handle
Multiple Releases of Same Resource or Handle represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.