CVE-2026-64116

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

ipv6: ioam: add NULL check for idev in ipv6_hop_ioam()

Reported by Sashiko:

The function ipv6_hop_ioam() accesses __in6_dev_get(skb->dev)->cnf.ioam6_enabled without validating the returned idev pointer. Because addrconf_ifdown() can concurrently clear dev->ip6_ptr via RCU, __in6_dev_get() can return NULL during interface teardown, which could cause a NULL pointer dereference when processing an IOAM Hop-by-Hop option.

Let's add a check and use SKB_DROP_REASON_IPV6DISABLED accordingly.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 12, 2026

Advisory Details (7)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

ipv6: ioam: add NULL check for idev in ipv6_hop_ioam() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: ioam: add NULL check for idev in ipv6_hop_ioam() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: ioam: add NULL check for idev in ipv6_hop_ioam() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: ioam: add NULL check for idev in ipv6_hop_ioam() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: ioam: add NULL check for idev in ipv6_hop_ioam() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/902daac307eb7e1955ce05b071950f3cba88c963
generic

ipv6: ioam: add NULL check for idev in ipv6_hop_ioam() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: ioam: add NULL check for idev in ipv6_hop_ioam() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/09cbfd4b81ae90963dadb1de99b63b702e73290a

Vendor Advisories for CVE-2026-64116(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

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

Frequently asked(5)

What is CVE-2026-64116?
CVE-2026-64116 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv6: ioam: add NULL check for idev in ipv6hopioam() Reported by Sashiko: The function ipv6hopioam() accesses in6devget(skb->dev)->cnf.ioam6_enabled without validating the returned idev pointer. Because addrconfifdown() can…
When was CVE-2026-64116 disclosed?
CVE-2026-64116 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-64116 actively exploited?
CVE-2026-64116 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64116?
CVE-2026-64116 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-64116?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64116, 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-64116

Explore →

Is Your Infrastructure Affected by CVE-2026-64116?

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

Start Free Scan →Browse All CVEs