CVE-2026-43038: Linux kernel · ipv6: icmp: clear skb2->cb[] in ip6_err_gen_icmpv6_unreach()
Affects Linux kernelSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 9.8 Critical · fixed in 3.13.0-214.265 : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.13.0-214.265, 4.4.0-1156.162, 4.15.0-1205.220~14.04.1 +123
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-8490-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8491-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8493-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8497-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8498-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8499-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8493-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8501-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8508-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-3 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinux-nvidiapkg:deb/ubuntu/linux-nvidia?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 25.10linuxpkg:deb/ubuntu/linux?arch=source&distro=questingOther threats | Affected
| Fixed in
|
Ubuntu 25.10linux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=questingOther threats | Affected
| Fixed in
|
Ubuntu 25.10linux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=questingOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- ubuntu.com/security/CVE-2026-43038 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-43038 (opens in a new tab)
- git.kernel.org/linus/86ab3e55673a7a49a841838776f1ab18d23a67b5 (opens in a new tab)
- ubuntu.com/security/notices/USN-8490-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8491-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8493-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8497-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8498-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8499-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8493-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8501-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8508-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8490-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-8527-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8528-1 (opens in a new tab)