CVE-2026-43186

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 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 heap buffer overflow in __ioam6_fill_trace_data()

On the receive path, __ioam6_fill_trace_data() uses trace->nodelen to decide how much data to write for each node. It trusts this field as-is from the incoming packet, with no consistency check against trace->type (the 24-bit field that tells which data items are present). A crafted packet can set nodelen=0 while setting type bits 0-21, causing the function to write ~100 bytes past the allocated region (into skb_shared_info), which corrupts adjacent heap memory and leads to a kernel panic.

Add a shared helper ioam6_trace_compute_nodelen() in ioam6.c to derive the expected nodelen from the type field, and use it:

  • in ioam6_iptunnel.c (send path, existing validation) to replace
the open-coded computation;
  • in exthdrs.c (receive path, ipv6_hop_ioam) to drop packets whose
nodelen is inconsistent with the type field, before any data is written.

Per RFC 9197, bits 12-21 are each short (4-octet) fields, so they are included in IOAM6_MASK_SHORT_FIELDS (changed from 0xff100000 to 0xff1ffc00).

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
46.6%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 11, 2026

Advisory Details (7)

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

ipv6: ioam: fix heap buffer overflow in __ioam6_fill_trace_data() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: ioam: fix heap buffer overflow in __ioam6_fill_trace_data() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: ioam: fix heap buffer overflow in __ioam6_fill_trace_data() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: ioam: fix heap buffer overflow in __ioam6_fill_trace_data() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: ioam: fix heap buffer overflow in __ioam6_fill_trace_data() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6db8b56eed62baacaf37486e83378a72635c04cc
generic

ipv6: ioam: fix heap buffer overflow in __ioam6_fill_trace_data() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/632d233cf2e64a46865ae2c064ae3c9df7c8864f
generic

ipv6: ioam: fix heap buffer overflow in __ioam6_fill_trace_data() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0591d6509c2ff13f09ea2998434aba0c0472e978

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 33× 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 229 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43186?
CVE-2026-43186 is a critical vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv6: ioam: fix heap buffer overflow in ioam6filltrace_data() On the receive path, ioam6filltrace_data() uses trace->nodelen to decide how much data to write for each node. It trusts this field as-is from the incoming packet, with…
When was CVE-2026-43186 disclosed?
CVE-2026-43186 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43186 actively exploited?
CVE-2026-43186 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 46.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43186?
CVE-2026-43186 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-43186?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43186, 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

Explore the affected products and dependency analysis for CVE-2026-43186

Explore →

Is Your Infrastructure Affected by CVE-2026-43186?

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