LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46084: RDMA/mana_ib: Disable RX steering on RSS QP destroy

In the Linux kernel, the following vulnerability has been resolved: RDMA/mana_ib: Disable RX steering on RSS QP destroy When an RSS QP is destroyed (e.g. DPDK exit), mana_ib_destroy_qp_rss() destroys the RX WQ objects but does not disable vPort RX steering in firmware. This leaves stale steering configuration that still points to the destroyed RX objects. If traffic continues to arrive (e.g. peer VM is still transmitting) and the VF interface is subsequently brought up (mana_open), the firmware may deliver completions using stale CQ IDs from the old RX objects. These CQ IDs can be reused by the ethernet driver for new TX CQs, causing RX completions to land on TX CQs: WARNING: mana_poll_tx_cq+0x1b8/0x220 [mana] (is_sq == false) WARNING: mana_gd_process_eq_events+0x209/0x290 (cq_table lookup fails) Fix this by disabling vPort RX steering before destroying RX WQ objects. Note that mana_fence_rqs() cannot be used here because the fence completion is delivered on the CQ, which is polled by user-mode (e.g. DPDK) and not visible to the kernel driver. Refactor the disable logic into a shared mana_disable_vport_rx() in mana_en, exported for use by mana_ib, replacing the duplicate code. The ethernet driver's mana_dealloc_queues() is also updated to call this common function.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can leave stale receive steering behind after an RDMA RSS queue pair is destroyed. Under continued traffic and later interface startup, completions may be delivered to the wrong completion queues, producing kernel warnings and unreliable network-driver behavior.

Executive priority

Treat this as a targeted infrastructure reliability risk, not a broadly proven remote compromise. Prioritize patching on Linux hosts that use the affected RDMA/network-driver path, especially production virtualized networking or DPDK environments.

Technical view

In mana_ib, mana_ib_destroy_qp_rss() destroyed RX work-queue objects without first disabling vPort RX steering in firmware. Stale steering could reference destroyed RX objects and reused CQ IDs, causing RX completions to appear on TX CQs. The fix disables vPort RX steering before RX WQ destruction and shares the logic through mana_en.

Likely exposure

Exposure appears limited to Linux systems using the mana_ib RDMA path with RSS QPs, such as DPDK-style user-mode operation on VF interfaces. The provided CVE data lists Linux as affected but does not provide CPEs or a CVSS score.

Exploitation context

The source describes a reliability failure when traffic continues after RSS QP destruction and the VF interface is later brought up. CISA KEV status is false, and the bundle provides no evidence of active exploitation or public weaponization.

Researcher notes

Evidence is strongest for a kernel driver state-management bug causing stale firmware steering and CQ reuse problems. Impact scope and severity remain incomplete because the bundle provides no CVSS, CWE, CPEs, distro advisories, or exploitation reports.

Mitigation direction

  • Apply Linux stable or distribution kernels containing the referenced mana_ib/mana_en fix.
  • Check Linux distribution and platform vendor advisories for backported fixed kernel versions.
  • Prioritize hosts using mana_ib RDMA, RSS QPs, DPDK, or VF networking.
  • Where patching is delayed, reduce risky restart cycles while peer traffic continues.
  • Monitor kernel logs for the cited mana_poll_tx_cq and mana_gd_process_eq_events warnings.

Validation and detection

  • Inventory running kernels and compare them with vendor fixed-version guidance.
  • Confirm whether mana and mana_ib drivers are loaded on exposed hosts.
  • Identify workloads that create and destroy RSS QPs, including DPDK exits.
  • Review kernel logs for warnings matching the CVE description.
  • Verify patched kernels include one of the referenced stable commits or a vendor backport.
Prepared
Confidence
medium
Sources
7

Public sources used

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-46084 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

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. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0266a177631d4c6b963b5b12dd986a8c5abdbf06, 0266a177631d4c6b963b5b12dd986a8c5abdbf06, 0266a177631d4c6b963b5b12dd986a8c5abdbf06, 0266a177631d4c6b963b5b12dd986a8c5abdbf06, 0266a177631d4c6b963b5b12dd986a8c5abdbf06unaffected
LinuxLinux6.2, 0, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.