CyberSecBulletin
CVE-2026-53137NVD status: Analyzed

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2026-53137 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 3c4444aec06c74fbc05661f370954ac814963c38, 91fb41218c413989d8b6c837748751454b452d68, 964e50ef7b8f09815a7d05b8326af700f8d5bc96 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.14% 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 3c4444aec06c74fbc05661f370954ac814963c38 or 91fb41218c413989d8b6c837748751454b452d68 or 964e50ef7b8f09815a7d05b8326af700f8d5bc96 or 79e0273272a05fb26f9b1e55bf1a52eefc3b7b35, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.259 or 5.15.210 or 6.1.176 or 6.6.143, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxeff682f83c9c2030761e7536c5d97e1b20f71c15 up to, but not including, 3c4444aec06c74fbc05661f370954ac814963c38; eff682f83c9c2030761e7536c5d97e1b20f71c15 up to, but not including, 91fb41218c413989d8b6c837748751454b452d68; eff682f83c9c2030761e7536c5d97e1b20f71c15 up to, but not including, 964e50ef7b8f09815a7d05b8326af700f8d5bc96; eff682f83c9c2030761e7536c5d97e1b20f71c15 up to, but not including, 79e0273272a05fb26f9b1e55bf1a52eefc3b7b35; eff682f83c9c2030761e7536c5d97e1b20f71c15 up to, but not including, bfba882cfcd08f6540f72f48e786b6404f5d2c5b; eff682f83c9c2030761e7536c5d97e1b20f71c15 up to, but not including, 1906064d50d194a145486e5caf3db3e708b6f6ef; eff682f83c9c2030761e7536c5d97e1b20f71c15 up to, but not including, 98cfb7530ea91d8e5e928285cdce58e1131f6e83; eff682f83c9c2030761e7536c5d97e1b20f71c15 up to, but not including, f0f3981c43b32cadfe373d636d9e9ca522bb3702; and 1 more ranges3c4444aec06c74fbc05661f370954ac814963c38, 91fb41218c413989d8b6c837748751454b452d68, 964e50ef7b8f09815a7d05b8326af700f8d5bc96, 79e0273272a05fb26f9b1e55bf1a52eefc3b7b35, bfba882cfcd08f6540f72f48e786b6404f5d2c5b, 1906064d50d194a145486e5caf3db3e708b6f6ef
LinuxLinux Kernel5.6 up to, but not including, 5.10.259; 5.11 up to, but not including, 5.15.210; 5.16 up to, but not including, 6.1.176; 6.2 up to, but not including, 6.6.143; 6.7 up to, but not including, 6.12.94; 6.13 up to, but not including, 6.18.36; 6.19 up to, but not including, 7.0.13; 7.15.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36

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: drm/amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size [Why & How] During HDCP 2.x repeater authentication over HDMI, the driver reads the sink's RxStatus register and extracts a 10-bit message size field (max value 1023). This value is used as the read length for the ReceiverID list without being clamped to the size of the destination buffer rx_id_list[177]. A malicious HDMI repeater could advertise a message size larger than the buffer, causing an out-of-bounds write during the I2C read. Clamp the read length in mod_hdcp_read_rx_id_list() to the size of the rx_id_list buffer, matching the approach already used in the DP branch. (cherry picked from commit 229212219e4247d9486f8ba41ef087358490be09)

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: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.