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

Published May 1, 2026
·
Updated

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 and passed to icmp6send(), it uses IP6CB(skb2).

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

If an attacker sends a forged ICMPv4 error with a CIPSO IP option, dsthao would be a non-zero offset. Inside icmp6send(), mip6addrswap() is called and uses ipv6findtlv(skb, opt->dsthao, IPV6TLVHAO).

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 ipv6destopthao.

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

Should the cb array also be cleared in ip6errgenicmpv6unreach() and ip6ip6err() to prevent this?

This patch implements the first suggestion.

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

Affected Software

23 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>3.13<5.10.253
Linux Linux kernel>=5.11<5.15.203
Linux Linux kernel>=5.16<6.1.168
Linux Linux kernel>=6.2<6.6.134
Linux Linux kernel>=6.7<6.12.81
Linux Linux kernel>=6.13<6.18.22
Linux Linux kernel>=6.19<6.19.12
Linux Linux kernel=3.13
Linux Linux kernel=3.13-rc3
Linux Linux kernel=3.13-rc4
Linux Linux kernel=3.13-rc5
Linux Linux kernel=3.13-rc6
Linux Linux kernel=3.13-rc7
Linux Linux kernel=3.13-rc8
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
Linux Linux kernel=7.0-rc6
debian/linux<=5.10.223-1
5.10.262-16.1.176-16.1.180-16.12.94-16.12.101-17.1.8-17.1.8-2
debian/linux-6.1
6.1.180-1~deb11u1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.262-1Fixed in 6.1.176-1Fixed in 6.1.180-1Fixed in 6.12.94-1Fixed in 6.12.101-1Fixed in 7.1.8-1Fixed in 7.1.8-2
  2. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.180-1~deb11u1
  3. Configuration

    In ip6_err_gen_icmpv6_unreach(), clear skb2->cb[] (IPv4 inet_skb_parm stored in cb) before skb2 is used, to prevent inet_skb_parm.opt overlapping with dsthao when later calling icmp6_send() / ipv6_find_tlv(skb, opt->dsthao, IPV6_TLV_HAO).

    Linux kernel (ipv6/icmp: ip6_err_gen_icmpv6_unreach) clear skb2->cb[] / IP6CB skb2 control buffer = clear
  4. Compensating control

    Ensure any paths that parse TLVs referenced by opt->dsthao (via ipv6_find_tlv with IPV6_TLV_HAO) verify that the remaining packet length can hold the full 18-byte struct ipv6_destopt_hao, so a forged ICMPv4 error with a non-zero CIPSO offset cannot cause searching beyond the available data.

Event History

May 1, 2026
CVE Published
via MITRE·02:15 PM
Data Sourced
via MITRE·02:15 PM
DescriptionSeverity
Data Sourced
via Red Hat·03:04 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 14, 2026
Data Sourced
via Ubuntu·09:45 PM
RemedyDescriptionSeverityAffected Software
Aug 16, 2026
Data Sourced
via Debian·09:49 PM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-43038?

CVE-2026-43038 has been classified as a medium severity vulnerability in the Linux kernel.

2

How do I fix CVE-2026-43038?

To resolve CVE-2026-43038, you should update your Linux kernel to the latest patched version provided by your distribution.

3

What impact does CVE-2026-43038 have on my system?

CVE-2026-43038 can potentially lead to denial of service conditions due to improper handling of ICMPv6 error packets.

4

Is CVE-2026-43038 a zero-day vulnerability?

CVE-2026-43038 is not a zero-day vulnerability as it has been disclosed and mitigated in updated kernel versions.

5

Which Linux kernel versions are affected by CVE-2026-43038?

CVE-2026-43038 affects specific older versions of the Linux kernel; refer to your distribution's advisory for details.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203