CVE-2026-43101

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

ipv6: ioam: fix potential NULL dereferences in __ioam6_fill_trace_data()

We need to check __in6_dev_get() for possible NULL value, as suggested by Yiming Qian.

Also add skb_dst_dev_rcu() instead of skb_dst_dev(), and two missing READ_ONCE().

Note that @dev can't be NULL.

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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

ipv6: ioam: fix potential NULL dereferences in __ioam6_fill_trace_data() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4e65a8b8daa18d63255ec58964dd192c7fdd9f8b
generic

ipv6: ioam: fix potential NULL dereferences in __ioam6_fill_trace_data() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4198aab6f000b4febb18ea820fea20634dd789c7
generic

ipv6: ioam: fix potential NULL dereferences in __ioam6_fill_trace_data() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3719c234fa94c37c955b1ecd3742ef280ec135e6

Vendor Advisories for CVE-2026-43101(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.18.24—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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc5-1~exp1 (160 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (126 versions)6.19.14-1—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-43101?
CVE-2026-43101 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv6: ioam: fix potential NULL dereferences in ioam6filltrace_data() We need to check in6devget() for possible NULL value, as suggested by Yiming Qian. Also add skbdstdevrcu() instead of skbdst_dev(), and two missing READ_ONCE().…
When was CVE-2026-43101 disclosed?
CVE-2026-43101 was first published in the National Vulnerability Database on May 6, 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-43101 actively exploited?
CVE-2026-43101 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 64.3% of all scored CVEs.
What is the CVSS score of CVE-2026-43101?
CVE-2026-43101 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-43101?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43101, 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-43101

Explore →

Is Your Infrastructure Affected by CVE-2026-43101?

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

Start Free Scan →Browse All CVEs