CyberSecBulletin
CVE-2026-23112NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2026-23112 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 0b9981751be14b59b4473383c731c833738aebdb, 42afe8ed8ad2de9c19457156244ef3e1eca94b5d, 1385be357e8acd09b36e026567f3a9d5c61139de 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.48% chance of exploitation within 30 days, which is low compared with other CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Linux to 0b9981751be14b59b4473383c731c833738aebdb or 42afe8ed8ad2de9c19457156244ef3e1eca94b5d or 1385be357e8acd09b36e026567f3a9d5c61139de or dca1a6ba0da9f472ef040525fab10fd9956db59f, whichever matches your release line, or a later version.
  2. Update RUGGEDCOM RST2428P to V4.0 or a later version.
  3. Update Linux Kernel to 5.10.250 or 5.15.200 or 6.1.163 or 6.6.124, whichever matches your release line, or a later version.
  4. 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
LinuxLinux872d26a391da92ed8f0c0f5cb5fef428067b7f30 up to, but not including, 0b9981751be14b59b4473383c731c833738aebdb; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 up to, but not including, 42afe8ed8ad2de9c19457156244ef3e1eca94b5d; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 up to, but not including, 1385be357e8acd09b36e026567f3a9d5c61139de; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 up to, but not including, dca1a6ba0da9f472ef040525fab10fd9956db59f; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 up to, but not including, 19672ae68d52ff75347ebe2420dde1b07adca09f; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 up to, but not including, ab200d71553bdcf4de554a5985b05b2dd606bc57; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 up to, but not including, 52a0a98549344ca20ad81a4176d68d28e3c05a5c; 5.00b9981751be14b59b4473383c731c833738aebdb, 42afe8ed8ad2de9c19457156244ef3e1eca94b5d, 1385be357e8acd09b36e026567f3a9d5c61139de, dca1a6ba0da9f472ef040525fab10fd9956db59f, 19672ae68d52ff75347ebe2420dde1b07adca09f, ab200d71553bdcf4de554a5985b05b2dd606bc57
SiemensRUGGEDCOM RST2428Pbefore V4.0V4.0
LinuxLinux Kernel5.0 up to, but not including, 5.10.250; 5.11 up to, but not including, 5.15.200; 5.16 up to, but not including, 6.1.163; 6.2 up to, but not including, 6.6.124; 6.7 up to, but not including, 6.12.70; 6.13 up to, but not including, 6.18.10; 6.195.10.250, 5.15.200, 6.1.163, 6.6.124, 6.12.70, 6.18.10

Version data comes from the organisation that assigned the CVE. 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 NVD.

Scoring systemScoreSeverityScored by
CVSS 3.19.8CriticalCNA
CVSS 3.19.8CriticalNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec nvmet_tcp_build_pdu_iovec() could walk past cmd->req.sg when a PDU length or offset exceeds sg_cnt and then use bogus sg->length/offset values, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining entries, and sg->length/offset before building the bvec.

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.