CyberSecBulletin
CVE-2026-46145NVD status: Modified

Linux: Buffer Copy without Checking Size of Input

Published Updated By the CyberSecBulletin desk

CVE-2026-46145 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 7d7c9f0fcd19c4d2f0164347c58d49cafa961b72, 11c1431d641e0e4e0529e96957995820600c7287, 012796f9541fcd0c1fa8ae4da7eb4d83931ef838 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.15% 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 7d7c9f0fcd19c4d2f0164347c58d49cafa961b72 or 11c1431d641e0e4e0529e96957995820600c7287 or 012796f9541fcd0c1fa8ae4da7eb4d83931ef838 or 7d94f155f354b961c598f71bafa804dceded513f, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.6.141 or 6.12.88 or 6.18.30 or 7.0.7, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux0266a177631d4c6b963b5b12dd986a8c5abdbf06 up to, but not including, 7d7c9f0fcd19c4d2f0164347c58d49cafa961b72; 0266a177631d4c6b963b5b12dd986a8c5abdbf06 up to, but not including, 11c1431d641e0e4e0529e96957995820600c7287; 0266a177631d4c6b963b5b12dd986a8c5abdbf06 up to, but not including, 012796f9541fcd0c1fa8ae4da7eb4d83931ef838; 0266a177631d4c6b963b5b12dd986a8c5abdbf06 up to, but not including, 7d94f155f354b961c598f71bafa804dceded513f; 0266a177631d4c6b963b5b12dd986a8c5abdbf06 up to, but not including, 6dd2d4ad9c8429523b1c220c5132bd551c006425; 6.27d7c9f0fcd19c4d2f0164347c58d49cafa961b72, 11c1431d641e0e4e0529e96957995820600c7287, 012796f9541fcd0c1fa8ae4da7eb4d83931ef838, 7d94f155f354b961c598f71bafa804dceded513f, 6dd2d4ad9c8429523b1c220c5132bd551c006425
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 8Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not 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 Enterprise Linux 6Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 7Not specified in the recordNot stated
LinuxLinux Kernel6.2 up to, but not including, 6.6.141; 6.7 up to, but not including, 6.12.88; 6.13 up to, but not including, 6.18.30; 6.19 up to, but not including, 7.0.7; 7.16.6.141, 6.12.88, 6.18.30, 7.0.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 CNA.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA
CVSS 3.17.0HighCNA

Official description

In the Linux kernel, the following vulnerability has been resolved: RDMA/mana: Validate rx_hash_key_len Sashiko points out that rx_hash_key_len comes from a uAPI structure and is blindly passed to memcpy, allowing the userspace to trash kernel memory. Bounds check it so the memcpy cannot overflow.

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.