CyberSecBulletin
CVE-2026-53195NVD status: Analyzed

Linux: Out-of-bounds Write

CVE-2026-53195 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 3e187152f44d76d7633a3855ffd0099e1588b82a, b7faf660eefa2047ebc2959ff76da2b6eae2e9e3, 2fd64bf0ad66ab5de0c73524591d879427ba5aba 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 3e187152f44d76d7633a3855ffd0099e1588b82a or b7faf660eefa2047ebc2959ff76da2b6eae2e9e3 or 2fd64bf0ad66ab5de0c73524591d879427ba5aba or 4cb722747ed25971f35cc47ce5c0e79d7f717713, 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
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 3e187152f44d76d7633a3855ffd0099e1588b82a; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, b7faf660eefa2047ebc2959ff76da2b6eae2e9e3; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 2fd64bf0ad66ab5de0c73524591d879427ba5aba; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 4cb722747ed25971f35cc47ce5c0e79d7f717713; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 130d6567eb148040eed1b73e1414ad6c27d22bd5; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 294692d3296eee3391c348d7ea6401916d27806c; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 5a79b634ee58786ca627268daefa7744f2af2e14; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 0fd2b00b2d3d05e3eaa13342b3dfb0fa85c226ae; and 1 more ranges3e187152f44d76d7633a3855ffd0099e1588b82a, b7faf660eefa2047ebc2959ff76da2b6eae2e9e3, 2fd64bf0ad66ab5de0c73524591d879427ba5aba, 4cb722747ed25971f35cc47ce5c0e79d7f717713, 130d6567eb148040eed1b73e1414ad6c27d22bd5, 294692d3296eee3391c348d7ea6401916d27806c
LinuxLinux Kernel2.6.12.1 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; 2.6.12; and 1 more ranges5.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: USB: serial: io_ti: fix heap overflow in build_i2c_fw_hdr() build_i2c_fw_hdr() allocates a fixed-size buffer of (16*1024 - 512) + sizeof(struct ti_i2c_firmware_rec) bytes, then copies le16_to_cpu(img_header->Length) bytes into it without validating that Length fits within the available space after the firmware record header. img_header->Length is a __le16 from the firmware file and can be up to 65535. check_fw_sanity() validates the total firmware size but not img_header->Length specifically. Fix by rejecting images where img_header->Length exceeds the available destination space.

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.