CVE-2026-46084
Last modified
CVE-2026-46084 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.2, < 6.6.140 |
| Linux | Linux Kernel | >= 6.7, < 6.12.86 |
| Linux | Linux Kernel | >= 6.13, < 6.18.27 |
| Linux | Linux Kernel | >= 6.19, < 7.0.4 |
References
Timeline
- Published
- Last Modified
- Status
- Undergoing Analysis
Frequently Asked Questions
What is CVE-2026-46084?
How severe is CVE-2026-46084?
How do I fix CVE-2026-46084?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-46079In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-4608The ProfileGrid – User Profiles, Groups and Communities plug…6.5
- CVE-2026-46080In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46081In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46082In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46083In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46085In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-46086In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46087In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46088In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46089In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-4609The ProfileGrid – User Profiles, Groups and Communities plug…7.1
Are you affected by CVE-2026-46084?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
