LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
12

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-46189 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
7CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H15.9redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7High
CVSS 3.1 vector shape for CVE-2026-46189Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Reported to Red Hat.

  3. ADP timelineredhat-SADP

    Made public.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

redhat-SADPkernel: RDMA/vmw_pvrdma: Fix double free on pvrdma_alloc_ucontext() error path
other:Red Hat severity ratingcvssV3_1
  • 2026-05-28T00:00:00.000Z: Reported to Red Hat.
  • 2026-05-28T00:00:00.000Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux29c8d9eba550c6d73d17cc1618a9f5f2a7345aa1, 29c8d9eba550c6d73d17cc1618a9f5f2a7345aa1, 29c8d9eba550c6d73d17cc1618a9f5f2a7345aa1, 29c8d9eba550c6d73d17cc1618a9f5f2a7345aa1, 29c8d9eba550c6d73d17cc1618a9f5f2a7345aa1, 29c8d9eba550c6d73d17cc1618a9f5f2a7345aa1, 29c8d9eba550c6d73d17cc1618a9f5f2a7345aa1, 29c8d9eba550c6d73d17cc1618a9f5f2a7345aa1unaffected
LinuxLinux4.10, 0, 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.88, 6.18.30, 7.0.7, 7.1affected
Weakness

CWE details

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.