CVE-2026-64035

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-19. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
9.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: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

igc: set tx buffer type for SMD frames

Sashiko pointed out that igc_fpe_init_smd_frame() initializes igc_tx_buffer fields for an SMD skb, but does not set the buffer type: https://sashiko.dev/#/patchset/20260415025226.114115-1-kohei%40enjuk.jp

Since igc_tx_buffer entries are reused, a stale XDP or XSK type can remain and make TX completion use the wrong cleanup path.

Set the buffer type to IGC_TX_BUFFER_TYPE_SKB.

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

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (3)

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

igc: set tx buffer type for SMD frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5acc641e590e008caaed480ed9ffae47cf7ecbdf
generic

igc: set tx buffer type for SMD frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c8587bd025244aa52061f5ceecbf5e68a1063d9
generic

igc: set tx buffer type for SMD frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1f83545f432d106d5fc71d3997b2d382104ebcc4

Vendor Advisories for CVE-2026-64035(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~24.04.1) @ noble2026-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—

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 60× in last 7d / 345× 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 417 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64035?
CVE-2026-64035 is a critical vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: igc: set tx buffer type for SMD frames Sashiko pointed out that igcfpeinitsmdframe() initializes igctxbuffer fields for an SMD skb, but does not set the buffer type:…
When was CVE-2026-64035 disclosed?
CVE-2026-64035 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64035 actively exploited?
CVE-2026-64035 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 63.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64035?
CVE-2026-64035 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64035?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64035, 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-64035

Explore →

Is Your Infrastructure Affected by CVE-2026-64035?

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

Start Free Scan →Browse All CVEs