CVE-2026-43038

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-01. 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: 0%CVSS: 9.8Exploit: NoneExposed: 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)
EPSS
17.1%
KEV
Not listed

Published

May 1, 2026

Last Modified

July 15, 2026

Advisory Details (10)

Auto-updated Jul 16, 2026
Patch available. Sources: redhat.
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
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/c438ba010171b70bad22fc18b1d5bdc3627476e8
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/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/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/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/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/0452b6526b2f54b2413b9cb4ff1ea2ac542c99c7

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
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:4.18.0-477.145.1.el8_82026-06-04redhat
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: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.

Weakness Classification(1)

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

Data Freshness Timeline

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

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

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 July 15, 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 17.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43038?
CVE-2026-43038 has a CVSS v3 base score of 9.8 (NVD).
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

Explore the affected products and dependency analysis for 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.