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.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Sep 9, 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/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/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/0591d6509c2ff13f09ea2998434aba0c0472e978
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/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

Patch Availability(28)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-40.40) @ questing2026-08-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1116.101) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.185.166) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1108.114~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1017.19) @ questing2026-08-23ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1026.26) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-08-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-08-23ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1028.28) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1074 (5.15.0-1074.78) @ jammy2026-08-23ubuntu
ubuntulinux-virtual-hwe-24.04 (6.17.0-40.40~24.04.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1021.21) @ questing2026-08-23ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1105.103) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1106.112~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1021.21~24.04.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1063.71~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-08-23ubuntu
redhatkernel-0:6.12.0-211.44.1.el10_22026-08-06redhat
linuxKernel @ 5.15.202osv

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 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (116 versions)6.19.6-1

Weakness Classification(1)

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

All Vendor Advisories

(25)

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 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 332 total refreshes for this CVE.

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

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 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-43186 actively exploited?
CVE-2026-43186 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 51.1% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.