CVE-2026-43445

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-08. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

e1000/e1000e: Fix leak in DMA error cleanup

If an error is encountered while mapping TX buffers, the driver should unmap any buffers already mapped for that skb.

Because count is incremented after a successful mapping, it will always match the correct number of unmappings needed when dma_error is reached. Decrementing count before the while loop in dma_error causes an off-by-one error. If any mapping was successful before an unsuccessful mapping, exactly one DMA mapping would leak.

In these commits, a faulty while condition caused an infinite loop in dma_error: Commit 03b1320dfcee ("e1000e: remove use of skb_dma_map from e1000e driver") Commit 602c0554d7b0 ("e1000: remove use of skb_dma_map from e1000 driver")

Commit c1fa347f20f1 ("e1000/e1000e/igb/igbvf/ixgb/ixgbe: Fix tests of unsigned in *_tx_map()") fixed the infinite loop, but introduced the off-by-one error.

This issue may still exist in the igbvf driver, but I did not address it in this patch.

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

Published

May 8, 2026

Last Modified

May 21, 2026

Advisory Details (8)

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

e1000/e1000e: Fix leak in DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

e1000/e1000e: Fix leak in DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

e1000/e1000e: Fix leak in DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7eaeb778bfaa3b2a804f89321c234d59c74569db
generic

e1000/e1000e: Fix leak in DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/519051c711dfd239ef6e4b28878efee400a035f9
generic

e1000/e1000e: Fix leak in DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/30e87ade8d678c25a8546cf38c0b498fa5cb27d3
generic

e1000/e1000e: Fix leak in DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10b5e65959e955a1c8894e0a5413944b5a70204a
generic

e1000/e1000e: Fix leak in DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0a1fc25deabab4efce64610e3c449485c4fa8f5f
generic

e1000/e1000e: Fix leak in DMA error cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0606c24a745bafd1be5d66c48361638cd9cad74b

Vendor Advisories for CVE-2026-43445(1)

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

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-23ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-23ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1063.71~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1107.113~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-23ubuntu
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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (119 versions)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 5× in last 7d / 59× 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 185 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-23 19:03 UTCEG score recompute
  11. 2026-08-23 19:03 UTCVendor advisory
  12. 2026-08-23 19:03 UTCGHSA enrichment
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 11:31 UTCEG score recompute
  19. 2026-08-17 11:31 UTCVendor advisory
  20. 2026-08-17 11:31 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 04:34 UTCEG score recompute
  23. 2026-08-16 04:34 UTCVendor advisory
  24. 2026-08-16 04:34 UTCGHSA enrichment
  25. 2026-08-16 02:14 UTCEPSS rescore
Show 75 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-15 01:16 UTCVendor advisory
  3. 2026-08-15 01:16 UTCGHSA enrichment
  4. 2026-08-14 03:08 UTCEG score recompute
  5. 2026-08-14 03:08 UTCVendor advisory
  6. 2026-08-14 03:08 UTCGHSA enrichment
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-12 21:32 UTCEG score recompute
  9. 2026-08-12 21:32 UTCVendor advisory
  10. 2026-08-12 21:32 UTCGHSA enrichment
  11. 2026-08-12 13:51 UTCEPSS rescore
  12. 2026-08-11 23:25 UTCEG score recompute
  13. 2026-08-11 23:25 UTCVendor advisory
  14. 2026-08-11 23:24 UTCGHSA enrichment
  15. 2026-08-11 13:43 UTCEPSS rescore
  16. 2026-08-11 01:17 UTCEG score recompute
  17. 2026-08-11 01:17 UTCVendor advisory
  18. 2026-08-11 01:17 UTCGHSA enrichment
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-10 00:31 UTCEG score recompute
  21. 2026-08-10 00:31 UTCVendor advisory
  22. 2026-08-10 00:31 UTCGHSA enrichment
  23. 2026-08-09 13:46 UTCEPSS rescore
  24. 2026-08-09 02:24 UTCEG score recompute
  25. 2026-08-09 02:24 UTCVendor advisory
  26. 2026-08-09 02:24 UTCGHSA enrichment
  27. 2026-08-08 16:37 UTCEPSS rescore
  28. 2026-08-07 18:23 UTCEG score recompute
  29. 2026-08-07 18:23 UTCVendor advisory
  30. 2026-08-07 18:23 UTCGHSA enrichment
  31. 2026-08-06 20:15 UTCEG score recompute
  32. 2026-08-06 20:15 UTCVendor advisory
  33. 2026-08-06 20:15 UTCGHSA enrichment
  34. 2026-08-06 13:46 UTCEPSS rescore
  35. 2026-08-05 22:08 UTCEG score recompute
  36. 2026-08-05 22:08 UTCVendor advisory
  37. 2026-08-05 22:07 UTCGHSA enrichment
  38. 2026-08-05 19:17 UTCEPSS rescore
  39. 2026-08-04 15:10 UTCEPSS rescore
  40. 2026-08-04 10:38 UTCEPSS rescore
  41. 2026-08-03 23:02 UTCEG score recompute
  42. 2026-08-03 23:02 UTCVendor advisory
  43. 2026-08-03 23:02 UTCGHSA enrichment
  44. 2026-08-03 10:36 UTCEPSS rescore
  45. 2026-08-03 00:54 UTCVendor advisory
  46. 2026-08-03 00:54 UTCGHSA enrichment
  47. 2026-08-02 02:45 UTCEG score recompute
  48. 2026-08-02 02:45 UTCVendor advisory
  49. 2026-08-02 02:45 UTCGHSA enrichment
  50. 2026-08-02 02:27 UTCEPSS rescore
  51. 2026-08-01 04:16 UTCEPSS rescore
  52. 2026-07-30 16:28 UTCEPSS rescore
  53. 2026-07-30 01:30 UTCEPSS rescore
  54. 2026-07-28 15:36 UTCEPSS rescore
  55. 2026-07-27 14:13 UTCEPSS rescore
  56. 2026-07-26 14:54 UTCEPSS rescore
  57. 2026-07-26 14:54 UTCEPSS rescore
  58. 2026-07-25 14:18 UTCEPSS rescore
  59. 2026-07-24 14:17 UTCEPSS rescore
  60. 2026-07-23 14:18 UTCEPSS rescore
  61. 2026-07-23 03:14 UTCEG score recompute
  62. 2026-07-22 14:08 UTCEPSS rescore
  63. 2026-07-21 15:24 UTCEPSS rescore
  64. 2026-07-20 17:08 UTCEPSS rescore
  65. 2026-07-19 14:31 UTCEPSS rescore
  66. 2026-07-19 02:29 UTCEPSS rescore
  67. 2026-07-18 10:04 UTCEPSS rescore
  68. 2026-07-16 17:03 UTCEPSS rescore
  69. 2026-07-16 05:19 UTCOSV refresh
  70. 2026-07-15 16:57 UTCEPSS rescore
  71. 2026-07-15 02:00 UTCEPSS rescore
  72. 2026-07-13 22:30 UTCEPSS rescore
  73. 2026-07-13 06:13 UTCEPSS rescore
  74. 2026-07-12 05:46 UTCEPSS rescore
  75. 2026-07-11 08:27 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43445?
CVE-2026-43445 is a medium vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: e1000/e1000e: Fix leak in DMA error cleanup If an error is encountered while mapping TX buffers, the driver should unmap any buffers already mapped for that skb. Because count is incremented after a successful mapping, it will…
When was CVE-2026-43445 disclosed?
CVE-2026-43445 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-43445 actively exploited?
CVE-2026-43445 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.7% of all scored CVEs.
What is the CVSS score of CVE-2026-43445?
CVE-2026-43445 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43445?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43445, 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-43445

Explore →

Is Your Infrastructure Affected by CVE-2026-43445?

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

Start Free Scan →Browse All CVEs