Linux: Out-of-bounds Read
CVE-2026-64014 is a high-severity out-of-bounds read vulnerability in Linux, with a CVSS 3.1 base score of 7.1 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 45c829e5eb3b974282bae50b7cca2cc891f74f0b, e7cdcb266ba06d8480809b78ab8bb2bf8ff51ccb, 95f47331dfde243f93e679ce70bd0c24b37c683d 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.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 45c829e5eb3b974282bae50b7cca2cc891f74f0b or e7cdcb266ba06d8480809b78ab8bb2bf8ff51ccb or 95f47331dfde243f93e679ce70bd0c24b37c683d or d883312061ccde8c536595998aaf687ec070077c, whichever matches your release line, or a later version.
- 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
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 5197424cdcccd2b0b1922babb93969b2515c43ce up to, but not including, 45c829e5eb3b974282bae50b7cca2cc891f74f0b; 5197424cdcccd2b0b1922babb93969b2515c43ce up to, but not including, e7cdcb266ba06d8480809b78ab8bb2bf8ff51ccb; 5197424cdcccd2b0b1922babb93969b2515c43ce up to, but not including, 95f47331dfde243f93e679ce70bd0c24b37c683d; 5197424cdcccd2b0b1922babb93969b2515c43ce up to, but not including, d883312061ccde8c536595998aaf687ec070077c; 5197424cdcccd2b0b1922babb93969b2515c43ce up to, but not including, 103d2de9f505f56da173e43f12dba62f92620278; 5197424cdcccd2b0b1922babb93969b2515c43ce up to, but not including, 0ca809ea8e0355299266c46e5f1755040aa8dcf3; 5197424cdcccd2b0b1922babb93969b2515c43ce up to, but not including, 7585b6aa55d8ac85ad22f522e1059f93507727b6; 5197424cdcccd2b0b1922babb93969b2515c43ce up to, but not including, 2905281cbda52ec9df540113b35b835feb5fafd3; and 1 more ranges | 45c829e5eb3b974282bae50b7cca2cc891f74f0b, e7cdcb266ba06d8480809b78ab8bb2bf8ff51ccb, 95f47331dfde243f93e679ce70bd0c24b37c683d, d883312061ccde8c536595998aaf687ec070077c, 103d2de9f505f56da173e43f12dba62f92620278, 0ca809ea8e0355299266c46e5f1755040aa8dcf3 |
| Linux | Linux Kernel | 2.6.34 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.93; 6.13 up to, but not including, 6.18.35; 6.19 up to, but not including, 7.0.12; 7.1 | 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93, 6.18.35 |
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
- NoneNothing can be modified.
- 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:N/A:H. Scored by NVD.
Official description
In the Linux kernel, the following vulnerability has been resolved: Input: usbtouchscreen - clamp NEXIO data_len/x_len to URB buffer size nexio_read_data() pulls data_len and x_len from a packed __be16 header in the device's interrupt packet and then walks packet->data[0..x_len) and packet->data[x_len..data_len) comparing each byte against a threshold. Both fields are 16-bit on the wire (max 65535). The existing adjustments shave at most 0x100 / 0x80 off, so the loop bound can still reach roughly 0xfeff. The URB transfer buffer for NEXIO is rept_size (1024) bytes from usb_alloc_coherent(), with the first 7 occupied by the packed header — so packet->data[] has 1017 valid bytes. read_data() callbacks are not given urb->actual_length, and nothing else bounds the walk. A device that lies about its length can get a ~64 KiB out-of-bounds read past the coherent DMA allocation. The first index whose byte exceeds NEXIO_THRESHOLD lands in begin_x / begin_y and from there into the reported touch coordinates, so adjacent kernel memory contents leak to userspace as ABS_X / ABS_Y events. Far enough out, the read can also hit an unmapped page and fault. Fix this all by clamping data_len to the buffer's data[] capacity and x_len to data_len.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that provides appropriate memory abstractions.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/0ca809ea8e0355299266c46e5f1755040aa8dcf3
- git.kernel.org/stable/c/103d2de9f505f56da173e43f12dba62f92620278
- git.kernel.org/stable/c/2905281cbda52ec9df540113b35b835feb5fafd3
- git.kernel.org/stable/c/45c829e5eb3b974282bae50b7cca2cc891f74f0b
- git.kernel.org/stable/c/7585b6aa55d8ac85ad22f522e1059f93507727b6
- git.kernel.org/stable/c/95f47331dfde243f93e679ce70bd0c24b37c683d
- git.kernel.org/stable/c/d883312061ccde8c536595998aaf687ec070077c
- git.kernel.org/stable/c/e7cdcb266ba06d8480809b78ab8bb2bf8ff51ccb
Recent Out-of-bounds Read vulnerabilities
- 7.1 High severity
- 7.8 High severity
- 7.3 High severity
- 7.1 High severity
- 7.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.