CVE-2026-46084
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2026
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 0266a177631d4c6b963b5b12dd986a8c5abdbf06 | affected | git | 6a2d6273b6c3581ce7b90ce17b5cbb4efd19438f | Unavailable | None listed |
| 0266a177631d4c6b963b5b12dd986a8c5abdbf06 | affected | git | f1ccc4d500a0b87a5599343fc2f798048836e184 | Unavailable | None listed |
| 0266a177631d4c6b963b5b12dd986a8c5abdbf06 | affected | git | 8ba804869382ce307f2a15f5f6f2adfd791f41dc | Unavailable | None listed |
| 0266a177631d4c6b963b5b12dd986a8c5abdbf06 | affected | git | 3be5ed233de03b00ae868cfc06e95331d8d9007c | Unavailable | None listed |
| 0266a177631d4c6b963b5b12dd986a8c5abdbf06 | affected | git | dbeb256e8dd87233d891b170c0b32a6466467036 | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 6.2 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 6.2 | Unavailable | None listed |
| 6.6.140 | unaffected | semver | Unavailable | 6.6.* | None listed |
| 6.12.86 | unaffected | semver | Unavailable | 6.12.* | None listed |
| 6.18.27 | unaffected | semver | Unavailable | 6.18.* | None listed |
| 7.0.4 | unaffected | semver | Unavailable | 7.0.* | None listed |
| 7.1 | unaffected | original_commit_for_fix | Unavailable | * | None listed |