CVE-2026-46126: RDMA/mana: Fix mana_destroy_wq_obj() cleanup in mana_ib_create_qp_rss()
In the Linux kernel, the following vulnerability has been resolved:
RDMA/mana: Fix mana_destroy_wq_obj() cleanup in mana_ib_create_qp_rss()
Sashiko points out there are two bugs here in the error unwind flow, both
related to how the WQ table is unwound.
First there is a double i-- on the first failure path due to the while loop
having a i--, remove it.
Second if mana_ib_install_cq_cb() fails then mana_create_wq_obj() is not
undone due to the above i--.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects cleanup logic in the RDMA/mana driver. When queue-pair RSS creation fails, the driver can unwind work-queue state incorrectly, including a double decrement and a missed cleanup. The public data does not provide CVSS, CWE, impact details, or active exploitation evidence.
Executive priority
Track and patch through normal kernel maintenance, with higher priority for Linux hosts using RDMA/mana. Current public evidence does not justify emergency treatment by itself.
Technical view
CVE-2026-46126 is an error-path cleanup bug in mana_ib_create_qp_rss(). The fix removes an extra index decrement and ensures mana_create_wq_obj() is undone when mana_ib_install_cq_cb() fails. The sources identify Linux kernel versions and stable commits, but do not describe a concrete security impact.
Likely exposure
Exposure is most likely on Linux systems using the RDMA/mana driver. Practical exposure depends on kernel version, enabled hardware or cloud network features, RDMA use, and distribution backports.
Exploitation context
The source bundle does not show KEV listing, public exploitation, exploit availability, or attacker prerequisites. Treat this as a kernel stability and cleanup correctness issue until vendor advisories clarify impact.
Researcher notes
The evidence is limited to the kernel fix description and stable commit references. The bug is in error unwind behavior, not a documented direct exploit primitive. Impact classification remains unclear without maintainer or vendor severity analysis.
Mitigation direction
Check Linux distribution advisories for CVE-2026-46126 coverage and fixed kernel packages.
Prioritize updates on systems using RDMA/mana or MANA-capable network paths.
Apply vendor-provided stable kernel fixes or supported distro backports.
If RDMA/mana is unnecessary, consider disabling it through supported operational controls.
Validation and detection
Inventory kernels and identify systems with RDMA/mana driver availability or usage.
Compare installed kernel builds against vendor advisories and stable fix references.
Confirm whether fixes are backported by checking distribution changelogs or package metadata.
Review kernel logs for RDMA/mana queue-pair creation or cleanup errors.
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.
cve · low confidence lookup
CVE-2026-46126 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 28, 2026, 09:35 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.