CVE-2026-46117: RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()
In the Linux kernel, the following vulnerability has been resolved:
RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()
Sashiko points out that the user can specify WQs sharing the same CQ as a
part of the uAPI and this will trigger the WARN_ON() then go on to corrupt
the kernel.
Just reject it outright and fail the QP creation.
Security readout for executives and security teams
Plain-English summary
A locally authenticated user with access to the Linux MANA RDMA interface may trigger unsafe kernel behavior, causing kernel memory corruption. Successful exploitation could compromise confidentiality, integrity, and availability of the host. Exposure depends on the affected kernel code and MANA RDMA functionality being available.
Executive priority
Prioritize affected multi-user, cloud, or compute hosts exposing MANA RDMA to less-trusted workloads. Patch promptly through normal emergency or high-severity kernel maintenance. Hosts without the affected driver path have lower immediate urgency, but applicability must be verified rather than assumed.
Technical view
The mana_ib_create_qp_rss() path accepted work queues sharing one completion queue. This user-controlled configuration triggered a WARN_ON() and execution continued into kernel corruption. The upstream resolution rejects the invalid configuration and fails queue-pair creation. CVSS 3.1 is 7.8: local, low complexity, low privileges, no user interaction, with high impacts.
Likely exposure
Highest risk applies to affected Linux kernels where the MANA RDMA driver and its userspace API are accessible to untrusted local users. The supplied version data identifies affected releases but contains ambiguous entries, so administrators should confirm applicability against their distribution advisory and installed kernel build.
Exploitation context
This is a local, low-privilege vulnerability rather than a directly remote flaw. The bundle reports no CISA KEV listing and provides no evidence of active exploitation. Exploitation would require access to the relevant RDMA userspace interface and could lead to kernel compromise or system failure.
Researcher notes
The core failure is continued execution after a user-triggerable WARN_ON(), followed by kernel corruption. The fix validates that work queues do not share the same completion queue. The supplied affected-version list is not a clear set of fixed ranges and includes duplicated commit identifiers; distribution-level package status should therefore govern remediation decisions.
Mitigation direction
Install the fixed kernel package provided by the operating-system vendor.
Review the listed Red Hat advisories for applicable product-specific updates.
Until patched, restrict untrusted local access to MANA RDMA interfaces where operationally feasible.
Reboot into the updated kernel and retire vulnerable kernel packages according to change policy.
Validation and detection
Record the running kernel version and compare it with the distribution's CVE advisory.
Confirm whether MANA RDMA functionality is present, enabled, and accessible to untrusted users.
Verify the installed kernel contains the vendor fix corresponding to the referenced stable commits.
After updating, confirm the host is running the fixed kernel rather than an older installed 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-1288: 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.
2CVSS vectors
5Timeline events
1ADP providers
12Source links
CVSS vector scores
2 official scores
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-1288 · source CWE mapping
Improper Validation of Consistency within Input
Improper Validation of Consistency within Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.