CVE-2026-43038

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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:

ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach()

Sashiko AI-review observed:

In ip6_err_gen_icmpv6_unreach(), the skb is an outer IPv4 ICMP error packet where its cb contains an IPv4 inet_skb_parm. When skb is cloned into skb2 and passed to icmp6_send(), it uses IP6CB(skb2).

IP6CB interprets the IPv4 inet_skb_parm as an inet6_skb_parm. The cipso offset in inet_skb_parm.opt directly overlaps with dsthao in inet6_skb_parm at offset 18.

If an attacker sends a forged ICMPv4 error with a CIPSO IP option, dsthao would be a non-zero offset. Inside icmp6_send(), mip6_addr_swap() is called and uses ipv6_find_tlv(skb, opt->dsthao, IPV6_TLV_HAO).

This would scan the inner, attacker-controlled IPv6 packet starting at that offset, potentially returning a fake TLV without checking if the remaining packet length can hold the full 18-byte struct ipv6_destopt_hao.

Could mip6_addr_swap() then perform a 16-byte swap that extends past the end of the packet data into skb_shared_info?

Should the cb array also be cleared in ip6_err_gen_icmpv6_unreach() and ip6ip6_err() to prevent this?

This patch implements the first suggestion.

I am not sure if ip6ip6_err() needs to be changed. A separate patch would be better anyway.

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
17%
KEV
Not listed

Published

May 1, 2026

Last Modified

September 8, 2026

Advisory Details (10)

Auto-updated Sep 15, 2026
No patch confirmed yet.
generic

ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/86ab3e55673a7a49a841838776f1ab18d23a67b5
generic

ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3d5127d998de617b130aae96b138dba22ac6a8a7
generic

ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0452b6526b2f54b2413b9cb4ff1ea2ac542c99c7
generic

ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c438ba010171b70bad22fc18b1d5bdc3627476e8
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions.

https://access.redhat.com/errata/RHSA-2026:22940
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions.

https://access.redhat.com/errata/RHSA-2026:22900

Vendor Advisories for CVE-2026-43038(20)

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

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-lts-xenial (4.4.0.283.289) @ xenial2026-09-08ubuntu
ubuntulinux-tools-azure (4.15.0.1205.220~14.04.1) @ trusty2026-09-08ubuntu
ubuntulinux-tools-aws-hwe (4.15.0.1195.208~16.04.1) @ xenial2026-09-08ubuntu
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-08ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1028.28) @ noble2026-09-08ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1144.175) @ focal2026-09-08ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-09-08ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1108.114~20.04.1) @ focal2026-09-08ubuntu
ubuntulinux-virtual-hwe-24.04 (6.17.0-40.40~24.04.1) @ noble2026-09-08ubuntu
ubuntulinux-tools-kvm-5.4 (5.4.0.1148.144) @ focal2026-09-08ubuntu
redhatkpatch-patch2026-08-19redhat
redhatkernel-0:5.14.0-687.19.1.el9_82026-06-29redhat
redhatkernel-0:6.12.0-211.28.1.el10_22026-06-25redhat
redhatkernel-0:4.18.0-305.194.1.el8_42026-06-17redhat
redhatkernel-0:4.18.0-372.195.1.el8_62026-06-12redhat
redhatkernel-0:4.18.0-553.132.1.el8_102026-06-10redhat
redhatkernel-rt-0:4.18.0-553.132.1.rt7.473.el8_102026-06-10redhat
redhatkernel-0:6.12.0-55.77.1.el10_02026-06-08redhat
redhatkernel-0:5.14.0-427.129.1.el9_42026-06-04redhat
redhatkernel-0:5.14.0-570.119.1.el9_62026-06-04redhat
redhatkernel-0:4.18.0-477.145.1.el8_82026-06-04redhat
redhatkernel-0:5.14.0-284.174.1.el9_22026-06-03redhat
redhatkernel-rt-0:5.14.0-284.174.1.rt14.459.el9_22026-06-03redhat
linuxKernel @ 5.10.253osv

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
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 (125 versions)6.19.12-1

Weakness Classification(1)

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

Additional Vendor Advisories

(6)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43038?
CVE-2026-43038 is a critical vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv6: icmp: clear skb2->cb[] in ip6errgenicmpv6unreach() Sashiko AI-review observed: In ip6errgenicmpv6unreach(), the skb is an outer IPv4 ICMP error packet where its cb contains an IPv4 inetskbparm. When skb is cloned into skb2…
When was CVE-2026-43038 disclosed?
CVE-2026-43038 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43038 actively exploited?
CVE-2026-43038 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 82.5% of all scored CVEs.
What is the CVSS score of CVE-2026-43038?
CVE-2026-43038 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-43038?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43038, 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-43038

Explore →

Is Your Infrastructure Affected by CVE-2026-43038?

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