CVE-2026-46084

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 24, 2026

Advisory Details (5)

Auto-updated Jun 24, 2026
No patch confirmed yet.
generic

RDMA/mana_ib: Disable RX steering on RSS QP destroy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f1ccc4d500a0b87a5599343fc2f798048836e184
generic

RDMA/mana_ib: Disable RX steering on RSS QP destroy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dbeb256e8dd87233d891b170c0b32a6466467036
generic

RDMA/mana_ib: Disable RX steering on RSS QP destroy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ba804869382ce307f2a15f5f6f2adfd791f41dc
generic

RDMA/mana_ib: Disable RX steering on RSS QP destroy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6a2d6273b6c3581ce7b90ce17b5cbb4efd19438f
generic

RDMA/mana_ib: Disable RX steering on RSS QP destroy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3be5ed233de03b00ae868cfc06e95331d8d9007c

Vendor Advisories for CVE-2026-46084(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(22)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1063.71~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-25ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-08-25ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1056.57~22.04.2) @ jammy2026-08-25ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1021.21~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-08-25ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.86-1~bpo12+1 (19 versions)6.12.86-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (131 versions)7.0.4-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(22)

Data Freshness Timeline

(refreshed 5× in last 7d / 87× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 242 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 05:20 UTCEG score recompute
  11. 2026-08-25 05:20 UTCVendor advisory
  12. 2026-08-25 05:20 UTCGHSA enrichment
  13. 2026-08-23 15:05 UTCEG score recompute
  14. 2026-08-23 15:05 UTCVendor advisory
  15. 2026-08-23 15:05 UTCGHSA enrichment
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-21 20:36 UTCEG score recompute
  19. 2026-08-21 20:36 UTCVendor advisory
  20. 2026-08-21 20:36 UTCGHSA enrichment
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 22:36 UTCVendor advisory
  23. 2026-08-20 22:36 UTCGHSA enrichment
  24. 2026-08-20 11:22 UTCEG score recompute
  25. 2026-08-20 11:22 UTCVendor advisory
Show 75 more
  1. 2026-08-20 11:22 UTCGHSA enrichment
  2. 2026-08-19 17:04 UTCEPSS rescore
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-17 09:17 UTCVendor advisory
  6. 2026-08-17 09:17 UTCGHSA enrichment
  7. 2026-08-16 15:14 UTCVendor advisory
  8. 2026-08-16 15:14 UTCGHSA enrichment
  9. 2026-08-16 02:50 UTCEG score recompute
  10. 2026-08-16 02:50 UTCVendor advisory
  11. 2026-08-16 02:50 UTCGHSA enrichment
  12. 2026-08-16 02:14 UTCEPSS rescore
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 23:05 UTCVendor advisory
  15. 2026-08-14 23:05 UTCGHSA enrichment
  16. 2026-08-14 12:16 UTCVendor advisory
  17. 2026-08-14 12:16 UTCGHSA enrichment
  18. 2026-08-14 01:27 UTCEG score recompute
  19. 2026-08-14 01:27 UTCVendor advisory
  20. 2026-08-14 01:27 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 09:08 UTCVendor advisory
  23. 2026-08-13 09:07 UTCGHSA enrichment
  24. 2026-08-12 22:18 UTCEG score recompute
  25. 2026-08-12 22:18 UTCVendor advisory
  26. 2026-08-12 22:18 UTCGHSA enrichment
  27. 2026-08-12 13:51 UTCEPSS rescore
  28. 2026-08-12 11:29 UTCVendor advisory
  29. 2026-08-12 11:29 UTCGHSA enrichment
  30. 2026-08-12 00:27 UTCEG score recompute
  31. 2026-08-12 00:27 UTCVendor advisory
  32. 2026-08-12 00:27 UTCGHSA enrichment
  33. 2026-08-11 13:35 UTCVendor advisory
  34. 2026-08-11 13:35 UTCGHSA enrichment
  35. 2026-08-11 00:13 UTCEG score recompute
  36. 2026-08-11 00:13 UTCVendor advisory
  37. 2026-08-11 00:12 UTCGHSA enrichment
  38. 2026-08-11 00:00 UTCEPSS rescore
  39. 2026-08-10 05:49 UTCVendor advisory
  40. 2026-08-10 05:49 UTCGHSA enrichment
  41. 2026-08-09 19:01 UTCEG score recompute
  42. 2026-08-09 19:01 UTCVendor advisory
  43. 2026-08-09 19:01 UTCGHSA enrichment
  44. 2026-08-09 13:46 UTCEPSS rescore
  45. 2026-08-09 08:12 UTCVendor advisory
  46. 2026-08-09 08:12 UTCGHSA enrichment
  47. 2026-08-08 21:23 UTCEG score recompute
  48. 2026-08-08 21:23 UTCVendor advisory
  49. 2026-08-08 21:23 UTCGHSA enrichment
  50. 2026-08-08 16:37 UTCEPSS rescore
  51. 2026-08-08 03:32 UTCVendor advisory
  52. 2026-08-08 03:32 UTCGHSA enrichment
  53. 2026-08-07 16:43 UTCVendor advisory
  54. 2026-08-07 16:43 UTCGHSA enrichment
  55. 2026-08-07 05:54 UTCVendor advisory
  56. 2026-08-07 05:54 UTCGHSA enrichment
  57. 2026-08-06 18:31 UTCEG score recompute
  58. 2026-08-06 18:31 UTCVendor advisory
  59. 2026-08-06 18:31 UTCGHSA enrichment
  60. 2026-08-06 13:47 UTCEPSS rescore
  61. 2026-08-06 07:42 UTCVendor advisory
  62. 2026-08-06 07:42 UTCGHSA enrichment
  63. 2026-08-05 20:53 UTCEG score recompute
  64. 2026-08-05 20:53 UTCVendor advisory
  65. 2026-08-05 20:53 UTCGHSA enrichment
  66. 2026-08-05 19:17 UTCEPSS rescore
  67. 2026-08-04 15:10 UTCEPSS rescore
  68. 2026-08-04 10:39 UTCEPSS rescore
  69. 2026-08-04 03:16 UTCVendor advisory
  70. 2026-08-04 03:16 UTCGHSA enrichment
  71. 2026-08-03 16:27 UTCEG score recompute
  72. 2026-08-03 16:27 UTCVendor advisory
  73. 2026-08-03 16:27 UTCGHSA enrichment
  74. 2026-08-03 10:36 UTCEPSS rescore
  75. 2026-08-02 23:46 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-46084?
CVE-2026-46084 is a high vulnerability published on May 27, 2026. 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), manaibdestroyqprss() destroys the RX WQ objects but does not disable vPort RX steering in firmware. This leaves stale steering…
When was CVE-2026-46084 disclosed?
CVE-2026-46084 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46084 actively exploited?
CVE-2026-46084 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-46084?
CVE-2026-46084 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46084?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46084, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46084

Explore →

Is Your Infrastructure Affected by CVE-2026-46084?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.