CyberSecBulletin
CVE-2026-68452NVD status: Received

Linux: Buffer Copy without Checking Size of Input

Published Updated By the CyberSecBulletin desk

CVE-2026-68452 is a high-severity buffer copy without checking size of input 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 be037204e4f595e4bd2159acda146677a1dc6342, 4e500ecb6704d879f9c2417c2ed6faba595015ca, 7f9e5a3dbb14a9b321a1dfa30390402c673f82dc 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 be037204e4f595e4bd2159acda146677a1dc6342 or 4e500ecb6704d879f9c2417c2ed6faba595015ca or 7f9e5a3dbb14a9b321a1dfa30390402c673f82dc or 406b317ea2b501f6f5eca1264293c9399a73a778, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd up to, but not including, be037204e4f595e4bd2159acda146677a1dc6342; 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd up to, but not including, 4e500ecb6704d879f9c2417c2ed6faba595015ca; 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd up to, but not including, 7f9e5a3dbb14a9b321a1dfa30390402c673f82dc; 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd up to, but not including, 406b317ea2b501f6f5eca1264293c9399a73a778; 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd up to, but not including, 4fc46deceda076d429ef3fab2ccf8d96629ebd23; 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd up to, but not including, ad93a1f1a45652478c0cf4eb029114e03af57f3b; 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd up to, but not including, 3859f630b674801a00bca39bc451f52288591f65; 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd up to, but not including, 06afe425d5283b9764303de47f554da5a808ce8a; and 1 more rangesbe037204e4f595e4bd2159acda146677a1dc6342, 4e500ecb6704d879f9c2417c2ed6faba595015ca, 7f9e5a3dbb14a9b321a1dfa30390402c673f82dc, 406b317ea2b501f6f5eca1264293c9399a73a778, 4fc46deceda076d429ef3fab2ccf8d96629ebd23, ad93a1f1a45652478c0cf4eb029114e03af57f3b

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 CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: s390/zcrypt: Validate length for CCA AES cipher key requests cca_cipher2protkey() derives the copy length for the CPRB parameter block directly from the length field in the key token. Reject the request early if the token length exceeds the available space in the parameter block.

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

The underlying weakness: Buffer Copy without Checking Size of Input

The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output 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 Buffer Copy without Checking Size of Input vulnerabilities (CWE-120)

Timeline

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

References

Recent Buffer Copy without Checking Size of Input vulnerabilities

Spotted an error? Tell us.