CVE-2026-43037: ip6_tunnel: clear skb2->cb[] in ip4ip6_err()

Published May 1, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ip6tunnel: clear skb2->cb[] in ip4ip6err()

Oskar Kjos reported the following problem.

ip4ip6err() calls icmpsend() on a cloned skb whose cb[] was written by the IPv6 receive path as struct inet6skbparm. icmpsend() passes IPCB(skb2) to ipoptionsecho(), which interprets that cb[] region as struct inetskbparm (IPv4). The layouts differ: inet6skbparm.nhoff at offset 14 overlaps inetskbparm.opt.rr, producing a non-zero rr value. ipoptionsecho() then reads optlen from attacker-controlled packet data at sptr[rr+1] and copies that many bytes into dopt->data, a fixed 40-byte stack buffer (IPOPTIONSDATAFIXEDSIZE).

To fix this we clear skb2->cb[], as suggested by Oskar Kjos.

Also add minimal IPv4 header validation (version == 4, ihl >= 5).

Affected Software

16 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=2.6.22<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=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

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:01 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-43037?

The severity of CVE-2026-43037 is classified as medium due to potential impact on the Linux kernel's handling of network packets.

2

How do I fix CVE-2026-43037?

To fix CVE-2026-43037, update your Linux kernel to the latest version where the vulnerability has been patched.

3

What impact does CVE-2026-43037 have on systems?

CVE-2026-43037 can lead to potential information leakage or denial-of-service conditions in affected systems running the Linux kernel.

4

Which versions of the Linux kernel are affected by CVE-2026-43037?

CVE-2026-43037 affects unspecified versions of the Linux kernel prior to the patch release.

5

Who reported CVE-2026-43037?

CVE-2026-43037 was reported by Oskar Kjos, highlighting an issue with the ip4ip6_err() function in the Linux kernel.

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