CVE-2026-43037: Linux kernel · ip6_tunnel: clear skb2->cb[] in ip4ip6_err()
Affects Linux kernelSource GCVE Database
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, 14:05 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% 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: ip6_tunnel: clear skb2->cb[] in ip4ip6_err() Oskar Kjos reported the following problem. ip4ip6_err() calls icmp_send() on a cloned skb whose cb[] was written by the IPv6 receive path as struct inet6_skb_parm. icmp_send() passes IPCB(skb2) to __ip_options_echo(), which interprets that cb[] region as struct inet_skb_parm (IPv4). The layouts differ: inet6_skb_parm.nhoff at offset 14 overlaps inet_skb_parm.opt.rr, producing a non-zero rr value. __ip_options_echo() 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 (IP_OPTIONS_DATA_FIXED_SIZE). To fix this we clear skb2->cb[], as suggested by Oskar Kjos. Also add minimal IPv4 header validation (version == 4, ihl >= 5).
References
- ubuntu.com/security/CVE-2026-43037 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-43037 (opens in a new tab)
- git.kernel.org/linus/2edfa31769a4add828a7e604b21cb82aaaa05925 (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)