CyberSecBulletin
CVE-2026-23422NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2026-23422 is a high-severity out-of-bounds write vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 7def51cb9fb8b8d5342443372b8cf28d8fbd7f3d, b5bababe7703a7322bc59b803ab1587887a2a5e4, c7becfe3e604d138bd53b8ac3111b2b3e8ec6b0e 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.13% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 7def51cb9fb8b8d5342443372b8cf28d8fbd7f3d or b5bababe7703a7322bc59b803ab1587887a2a5e4 or c7becfe3e604d138bd53b8ac3111b2b3e8ec6b0e or fa4412cdc5178a48799bafcb8af28fd2fbf3d703, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.15.203 or 6.1.167 or 6.6.130 or 6.12.77, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux77611cab5bdfff7a070ae574bbfba20a1de99d1b up to, but not including, 7def51cb9fb8b8d5342443372b8cf28d8fbd7f3d; 34b56c16efd61325d80bf1d780d0e176be662f59 up to, but not including, b5bababe7703a7322bc59b803ab1587887a2a5e4; f89e33c9c37f0001b730e23b3b05ab7b1ecface2 up to, but not including, c7becfe3e604d138bd53b8ac3111b2b3e8ec6b0e; 2447edc367800ba914acf7ddd5d250416b45fb31 up to, but not including, fa4412cdc5178a48799bafcb8af28fd2fbf3d703; 1b381a638e1851d8cfdfe08ed9cdbec5295b18c9 up to, but not including, 00f42ace446f1e4bf84988f2281131f52cd32796; 31a7a0bbeb006bac2d9c81a2874825025214b6d8 up to, but not including, 28fd8ac1d49389cb230d712116f54e27ebec11b8; 31a7a0bbeb006bac2d9c81a2874825025214b6d8 up to, but not including, 74badb9c20b1a9c02a95c735c6d3cd6121679c93; 5.15.200 up to, but not including, 5.15.203; and 5 more ranges7def51cb9fb8b8d5342443372b8cf28d8fbd7f3d, b5bababe7703a7322bc59b803ab1587887a2a5e4, c7becfe3e604d138bd53b8ac3111b2b3e8ec6b0e, fa4412cdc5178a48799bafcb8af28fd2fbf3d703, 00f42ace446f1e4bf84988f2281131f52cd32796, 28fd8ac1d49389cb230d712116f54e27ebec11b8
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)V3.1.6 and later; V3.1.5 and later; V3.1.7 and laterNot stated
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)V3.1.6 and later; V3.1.5 and later; V3.1.7 and laterNot stated
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)V3.1.6 and later; V3.1.5 and later; V3.1.7 and laterNot stated
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)V3.1.6 and later; V3.1.5 and later; V3.1.7 and laterNot stated
SiemensSIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)V3.1.6 and later; V3.1.5 and later; V3.1.7 and laterNot stated
LinuxLinux Kernel5.15.200 up to, but not including, 5.15.203; 6.1.163 up to, but not including, 6.1.167; 6.6.124 up to, but not including, 6.6.130; 6.12.70 up to, but not including, 6.12.77; 6.18.10 up to, but not including, 6.18.17; 6.19.1 up to, but not including, 6.19.7; 6.19; 7.05.15.203, 6.1.167, 6.6.130, 6.12.77, 6.18.17, 6.19.7

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
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Official description

In the Linux kernel, the following vulnerability has been resolved: dpaa2-switch: Fix interrupt storm after receiving bad if_id in IRQ handler Commit 31a7a0bbeb00 ("dpaa2-switch: add bounds check for if_id in IRQ handler") introduces a range check for if_id to avoid an out-of-bounds access. If an out-of-bounds if_id is detected, the interrupt status is not cleared. This may result in an interrupt storm. Clear the interrupt status after detecting an out-of-bounds if_id to avoid the problem. Found by an experimental AI code review agent at Google.

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. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.