CVE-2026-43466

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

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

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery

In case of a TX error CQE, a recovery flow is triggered, mlx5e_reset_txqsq_cc_pc() resets dma_fifo_cc to 0 but not dma_fifo_pc, desyncing the DMA FIFO producer and consumer.

After recovery, the producer pushes new DMA entries at the old dma_fifo_pc, while the consumer reads from position 0. This causes us to unmap stale DMA addresses from before the recovery.

The DMA FIFO is a purely software construct with no HW counterpart. At the point of reset, all WQEs have been flushed so dma_fifo_cc is already equal to dma_fifo_pc. There is no need to reset either counter, similar to how skb_fifo pc/cc are untouched.

Remove the 'dma_fifo_cc = 0' reset.

This fixes the following WARNING: WARNING: CPU: 0 PID: 0 at drivers/iommu/dma-iommu.c:1240 iommu_dma_unmap_page+0x79/0x90 Modules linked in: mlx5_vdpa vringh vdpa bonding mlx5_ib mlx5_vfio_pci ipip mlx5_fwctl tunnel4 mlx5_core ib_ipoib geneve ip6_gre ip_gre gre nf_tables ip6_tunnel rdma_ucm ib_uverbs ib_umad vfio_pci vfio_pci_core act_mirred act_skbedit act_vlan vhost_net vhost tap ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_mangle cls_matchall nfnetlink_cttimeout act_gact cls_flower sch_ingress vhost_iotlb iptable_raw tunnel6 vfio_iommu_type1 vfio openvswitch nsh rpcsec_gss_krb5 auth_rpcgss oid_registry xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink iptable_nat nf_nat xt_addrtype br_netfilter overlay zram zsmalloc rpcrdma ib_iser libiscsi scsi_transport_iscsi rdma_cm iw_cm ib_cm ib_core fuse [last unloaded: nf_tables] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.13.0-rc5_for_upstream_min_debug_2024_12_30_21_33 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:iommu_dma_unmap_page+0x79/0x90 Code: 2b 4d 3b 21 72 26 4d 3b 61 08 73 20 49 89 d8 44 89 f9 5b 4c 89 f2 4c 89 e6 48 89 ef 5d 41 5c 41 5d 41 5e 41 5f e9 c7 ae 9e ff <0f> 0b 5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 2e 0f 1f 84 00 00 00 00 Call Trace: ? __warn+0x7d/0x110 ? iommu_dma_unmap_page+0x79/0x90 ? report_bug+0x16d/0x180 ? handle_bug+0x4f/0x90 ? exc_invalid_op+0x14/0x70 ? asm_exc_invalid_op+0x16/0x20 ? iommu_dma_unmap_page+0x79/0x90 ? iommu_dma_unmap_page+0x2e/0x90 dma_unmap_page_attrs+0x10d/0x1b0 mlx5e_tx_wi_dma_unmap+0xbe/0x120 [mlx5_core] mlx5e_poll_tx_cq+0x16d/0x690 [mlx5_core] mlx5e_napi_poll+0x8b/0xac0 [mlx5_core] __napi_poll+0x24/0x190 net_rx_action+0x32a/0x3b0 ? mlx5_eq_comp_int+0x7e/0x270 [mlx5_core] ? notifier_call_chain+0x35/0xa0 handle_softirqs+0xc9/0x270 irq_exit_rcu+0x71/0xd0 common_interrupt+0x7f/0xa0 asm_common_interrupt+0x22/0x40

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
42(Track)
EG Risk 42/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
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 21, 2026

Advisory Details (8)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c5ee9b981ee050b73fdf3f4a2464d6f1a8e10a8
generic

net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/829efcccfa8f69db5dc8332961295587d218cee6
generic

net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/821f85d619f7f22cda7b9d7de89cf5eeb1d11544
generic

net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/383b37c04a4827ba60b2bafc1a6cdfd995aed58f
generic

net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1633111d69053512d099658d4a05fc736fab36b0

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253—osv

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.

Data Freshness Timeline

(refreshed 9× in last 7d / 31× 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 118 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43466?
CVE-2026-43466 is a high vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery In case of a TX error CQE, a recovery flow is triggered, mlx5eresettxqsqccpc() resets dmafifocc to 0 but not dmafifopc, desyncing the DMA FIFO producer and consumer. After…
When was CVE-2026-43466 disclosed?
CVE-2026-43466 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43466 actively exploited?
CVE-2026-43466 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 74.7% of all scored CVEs.
What is the CVSS score of CVE-2026-43466?
CVE-2026-43466 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-43466?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43466, 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

Explore the affected products and dependency analysis for CVE-2026-43466

Explore →

Is Your Infrastructure Affected by CVE-2026-43466?

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

Start Free Scan →Browse All CVEs