CVE-2026-43466

HIGHNVD 8.28.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-28772 (ENISA EUVD) · GHSA-757p-mh2f-rf8w (GitHub Security Advisories)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.2HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 8, 2026

Last Modified

October 19, 2026

Advisory Details (8)

Auto-updated May 11, 2026
Patch available.
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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

Vendor Advisories for CVE-2026-43466(1)

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

Patch Availability(28)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-10-27ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1106.104) @ jammy2026-10-27ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-10-27ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-ibm-edge (6.8.0-1061.62~22.04.1) @ jammy2026-10-27ubuntu
linuxKernel @ 5.10.253 (fixes >=4.17.0)—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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)
  • every version up to 5.10.257-1: fixed in 5.10.257-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (123 versions)
  • every version up to 6.19.10-1: fixed in 6.19.10-1
—

Weakness Classification(1)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 48× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 281 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 181 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43466?
CVE-2026-43466 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-43466 published?
The CVE record for CVE-2026-43466 was published on May 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-43466 actively exploited?
CVE-2026-43466 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-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?
A fix for CVE-2026-43466 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43466 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs