CVE-2026-64110

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
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:

igc: fix potential skb leak in igc_fpe_xmit_smd_frame()

When igc_fpe_init_tx_descriptor() fails, no one takes care of an allocated skb, leaking it. [1] Use dev_kfree_skb_any() on failure.

Tested on an I226 adapter with the following command, while injecting faults in igc_fpe_init_tx_descriptor() to trigger the error path. # ethtool --set-mm $DEV verify-enabled on tx-enabled on pmac-enabled on

[1] unreferenced object 0xffff888113c6cdc0 (size 224): ... backtrace (crc be3d3fda): kmem_cache_alloc_node_noprof+0x3b1/0x410 __alloc_skb+0xde/0x830 igc_fpe_xmit_smd_frame.isra.0+0xad/0x1b0 igc_fpe_send_mpacket+0x37/0x90 ethtool_mmsv_verify_timer+0x15e/0x300

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

July 19, 2026

Last Modified

August 12, 2026

Advisory Details (3)

Auto-updated Aug 12, 2026
No patch confirmed yet.
generic

igc: fix potential skb leak in igc_fpe_xmit_smd_frame() - kernel/git/stable/linux.git - Linux kernel stable tree

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

igc: fix potential skb leak in igc_fpe_xmit_smd_frame() - kernel/git/stable/linux.git - Linux kernel stable tree

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

igc: fix potential skb leak in igc_fpe_xmit_smd_frame() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-64110(1)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

Weakness Classification(1)

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

All Vendor Advisories

(5)

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 22× in last 7d / 85× 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 115 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64110?
CVE-2026-64110 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: igc: fix potential skb leak in igcfpexmitsmdframe() When igcfpeinittxdescriptor() fails, no one takes care of an allocated skb, leaking it. [1] Use devkfreeskb_any() on failure. Tested on an I226 adapter with the following command,…
When was CVE-2026-64110 disclosed?
CVE-2026-64110 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64110 actively exploited?
CVE-2026-64110 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-64110?
CVE-2026-64110 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64110?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64110, 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-64110

Explore →

Is Your Infrastructure Affected by CVE-2026-64110?

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

Start Free Scan →Browse All CVEs