CyberSecBulletin
CVE-2026-64274NVD status: Analyzed

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2026-64274 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 e825f352ef5271255cd08cc994b0dc25648a2f38, 4bfea9c3a0981c1c7fc5d1a1b27197b2de247902, 98b2caef249183b572c04451365246f919707845 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.17% 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 e825f352ef5271255cd08cc994b0dc25648a2f38 or 4bfea9c3a0981c1c7fc5d1a1b27197b2de247902 or 98b2caef249183b572c04451365246f919707845 or 719d1a2c83a46be6bf81af905e4f6adb3d32dc28, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.261 or 5.15.212 or 6.1.178 or 6.6.145, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxa7ac7c95d4682883d141c5d7a7544d2818f0a09f up to, but not including, e825f352ef5271255cd08cc994b0dc25648a2f38; a7ac7c95d4682883d141c5d7a7544d2818f0a09f up to, but not including, 4bfea9c3a0981c1c7fc5d1a1b27197b2de247902; a7ac7c95d4682883d141c5d7a7544d2818f0a09f up to, but not including, 98b2caef249183b572c04451365246f919707845; a7ac7c95d4682883d141c5d7a7544d2818f0a09f up to, but not including, 719d1a2c83a46be6bf81af905e4f6adb3d32dc28; a7ac7c95d4682883d141c5d7a7544d2818f0a09f up to, but not including, 46addbd13dbf4aacb71cfbca964a5e552d0f45ae; a7ac7c95d4682883d141c5d7a7544d2818f0a09f up to, but not including, 3b32303460155603d25444274856013d211d5e1f; a7ac7c95d4682883d141c5d7a7544d2818f0a09f up to, but not including, 2a67668690129953e898923260a2dd1c7c196495; a7ac7c95d4682883d141c5d7a7544d2818f0a09f up to, but not including, 5ed62a96e06be4e94b8296b7932afee550a70e04; and 1 more rangese825f352ef5271255cd08cc994b0dc25648a2f38, 4bfea9c3a0981c1c7fc5d1a1b27197b2de247902, 98b2caef249183b572c04451365246f919707845, 719d1a2c83a46be6bf81af905e4f6adb3d32dc28, 46addbd13dbf4aacb71cfbca964a5e552d0f45ae, 3b32303460155603d25444274856013d211d5e1f
LinuxLinux Kernel4.1 up to, but not including, 5.10.261; 5.11 up to, but not including, 5.15.212; 5.16 up to, but not including, 6.1.178; 6.2 up to, but not including, 6.6.145; 6.7 up to, but not including, 6.12.96; 6.13 up to, but not including, 6.18.39; 6.19 up to, but not including, 7.1.45.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39

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: Input: goodix - clamp the device-reported contact count goodix_ts_read_input_report() copies the number of touch points reported by the device into an on-stack buffer u8 point_data[2 + GOODIX_MAX_CONTACT_SIZE * GOODIX_MAX_CONTACTS]; which is sized for at most GOODIX_MAX_CONTACTS (10) contacts. The only runtime check bounds the per-interrupt count against ts->max_touch_num, but that value is taken verbatim from a 4-bit field of the device configuration block and is never clamped: ts->max_touch_num = ts->config[MAX_CONTACTS_LOC] & 0x0f; The nibble can be 0..15, so a malfunctioning, malicious or counterfeit controller (or an attacker tampering with the I2C bus) can advertise up to 15 contacts. goodix_ts_read_input_report() then accepts a touch_num of up to 15 and the second goodix_i2c_read() writes ts->contact_size * (touch_num - 1) bytes past the one-contact header into point_data - up to 30 bytes (45 with the 9-byte report format) beyond the 92-byte buffer: a stack out-of-bounds write. Clamp max_touch_num to GOODIX_MAX_CONTACTS, the number of contacts point_data[] is sized for, when reading it from the configuration.

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.