CVE-2026-46084RDMA/mana_ib: Disable RX steering on RSS QP destroy
- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 14 days later
· 14 days later
Published
- 5 months later
· 5 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Undergoing Analysis | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (12 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 0266a177631d4c6b963b5b12dd986a8c5abdbf06 – < 6a2d6273b6c3581ce7b90ce17b5cbb4efd19438f
- affected 0266a177631d4c6b963b5b12dd986a8c5abdbf06 – < f1ccc4d500a0b87a5599343fc2f798048836e184
- affected 0266a177631d4c6b963b5b12dd986a8c5abdbf06 – < 8ba804869382ce307f2a15f5f6f2adfd791f41dc
- affected 0266a177631d4c6b963b5b12dd986a8c5abdbf06 – < 3be5ed233de03b00ae868cfc06e95331d8d9007c
- affected 0266a177631d4c6b963b5b12dd986a8c5abdbf06 – < dbeb256e8dd87233d891b170c0b32a6466467036
- affected 6.2
- unaffected < 6.2
- unaffected 6.6.140 – ≤ 6.6.*
- unaffected 6.12.86 – ≤ 6.12.*
- unaffected 6.18.27 – ≤ 6.18.*
- unaffected 7.0.4 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References5
- https://git.kernel.org/stable/c/6a2d6273b6c3581ce7b90ce17b5cbb4efd19438f (opens in a new tab)
- https://git.kernel.org/stable/c/f1ccc4d500a0b87a5599343fc2f798048836e184 (opens in a new tab)
- https://git.kernel.org/stable/c/8ba804869382ce307f2a15f5f6f2adfd791f41dc (opens in a new tab)
- https://git.kernel.org/stable/c/3be5ed233de03b00ae868cfc06e95331d8d9007c (opens in a new tab)
- https://git.kernel.org/stable/c/dbeb256e8dd87233d891b170c0b32a6466467036 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-32467 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-46084)Record last updated .