CyberSecBulletin
CVE-2026-43037NVD status: Modified

Linux: Out-of-bounds Write

CVE-2026-43037 is a critical-severity out-of-bounds write vulnerability in Linux, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions ea9f65b27c8404e164848ebff1443310fd187629, d6621f60192fe10c047a4487be42a6f4c150707f, 2cc6e3b0fe0f0242d1f530a93a4924f48ab85ba5 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.69% chance of exploitation within 30 days, higher than 53% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Linux to ea9f65b27c8404e164848ebff1443310fd187629 or d6621f60192fe10c047a4487be42a6f4c150707f or 2cc6e3b0fe0f0242d1f530a93a4924f48ab85ba5 or a0c4ce9900a108eaf55d0f3b399cb55999647d39, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.253 or 5.15.203 or 6.1.168 or 6.6.134, whichever matches your release line, or a later version.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxc4d3efafcc933fd2ffd169d7dc4f980393a13796 up to, but not including, ea9f65b27c8404e164848ebff1443310fd187629; c4d3efafcc933fd2ffd169d7dc4f980393a13796 up to, but not including, d6621f60192fe10c047a4487be42a6f4c150707f; c4d3efafcc933fd2ffd169d7dc4f980393a13796 up to, but not including, 2cc6e3b0fe0f0242d1f530a93a4924f48ab85ba5; c4d3efafcc933fd2ffd169d7dc4f980393a13796 up to, but not including, a0c4ce9900a108eaf55d0f3b399cb55999647d39; c4d3efafcc933fd2ffd169d7dc4f980393a13796 up to, but not including, 1063515ce15ff31065c4e7f8265f4c2fd3c54876; c4d3efafcc933fd2ffd169d7dc4f980393a13796 up to, but not including, 590f622669b97eaf7b57a1de7b0a6e68c5d8b2c3; c4d3efafcc933fd2ffd169d7dc4f980393a13796 up to, but not including, 4a622658f384b03560834cbe8ffcfe69a278f7c8; c4d3efafcc933fd2ffd169d7dc4f980393a13796 up to, but not including, 2edfa31769a4add828a7e604b21cb82aaaa05925; and 1 more rangesea9f65b27c8404e164848ebff1443310fd187629, d6621f60192fe10c047a4487be42a6f4c150707f, 2cc6e3b0fe0f0242d1f530a93a4924f48ab85ba5, a0c4ce9900a108eaf55d0f3b399cb55999647d39, 1063515ce15ff31065c4e7f8265f4c2fd3c54876, 590f622669b97eaf7b57a1de7b0a6e68c5d8b2c3
Red HatNVIDIA for RHEL 10Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 10Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 10.0 Extended Update SupportNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 6 Extended Lifecycle Support - EXTENSIONNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 7 Extended Lifecycle SupportNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8.4 Advanced Mission Critical Update SupportNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-OnNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8.6 Advanced Mission Critical Update SupportNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-OnNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8.8 Telecommunications Update ServiceNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8.8 Update Services for SAP SolutionsNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9.2 Update Services for SAP SolutionsNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9.4 Update Services for SAP SolutionsNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9.6 Extended Update SupportNot specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4.12Not specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4.13Not specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4.14Not specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4.15Not specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4.16Not specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4.17Not specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4.18Not specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4.19Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE; 4 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Scoring systemScoreSeverityScored by
CVSS 3.19.8CriticalCNA
CVSS 3.18.8HighCNA

Official 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).

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.