RDMA/mana_ib: Disable RX steering on RSS QP destroy
Summary
| CVE | CVE-2026-46084 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-05-27 14:17:29 UTC |
|---|
| Updated | 2026-05-27 14:48:03 UTC |
|---|
| 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. |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 0266a177631d4c6b963b5b12dd986a8c5abdbf06 6a2d6273b6c3581ce7b90ce17b5cbb4efd19438f git |
Not specified |
| CNA |
Linux |
Linux |
affected 0266a177631d4c6b963b5b12dd986a8c5abdbf06 f1ccc4d500a0b87a5599343fc2f798048836e184 git |
Not specified |
| CNA |
Linux |
Linux |
affected 0266a177631d4c6b963b5b12dd986a8c5abdbf06 8ba804869382ce307f2a15f5f6f2adfd791f41dc git |
Not specified |
| CNA |
Linux |
Linux |
affected 0266a177631d4c6b963b5b12dd986a8c5abdbf06 3be5ed233de03b00ae868cfc06e95331d8d9007c git |
Not specified |
| CNA |
Linux |
Linux |
affected 0266a177631d4c6b963b5b12dd986a8c5abdbf06 dbeb256e8dd87233d891b170c0b32a6466467036 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.2 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.2 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.140 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.86 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.27 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0.4 7.0.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/f1ccc4d500a0b87a5599343fc2f798048836e184 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/dbeb256e8dd87233d891b170c0b32a6466467036 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/3be5ed233de03b00ae868cfc06e95331d8d9007c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/8ba804869382ce307f2a15f5f6f2adfd791f41dc |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/6a2d6273b6c3581ce7b90ce17b5cbb4efd19438f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.
