CVE-2026-64014Input: usbtouchscreen - clamp NEXIO data_len/x_len to URB buffer size
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.1 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- Jul 19, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | 5197424cdcccd2b0b1922babb93969b2515c43ce builds before 45c829e5eb3b974282bae50b7cca2cc891f74f0b; from 5197424cdcccd2b0b1922babb93969b2515c43ce before e7cdcb266ba06d8480809b78ab8bb2bf8ff51ccb; 5197424cdcccd2b0b1922babb93969b2515c43ce builds before 95f47331dfde243f93e679ce70bd0c24b37c683d; from 5197424cdcccd2b0b1922babb93969b2515c43ce before d883312061ccde8c536595998aaf687ec070077c; 5197424cdcccd2b0b1922babb93969b2515c43ce builds before 103d2de9f505f56da173e43f12dba62f92620278; 5197424cdcccd2b0b1922babb93969b2515c43ce builds before 0ca809ea8e0355299266c46e5f1755040aa8dcf3; 5197424cdcccd2b0b1922babb93969b2515c43ce builds before 7585b6aa55d8ac85ad22f522e1059f93507727b6; 5197424cdcccd2b0b1922babb93969b2515c43ce builds before 2905281cbda52ec9df540113b35b835feb5fafd3 | CNA record |
linux linux_kernel linux:linux_kernel | from 2.6.34 before 5.10.259; from 5.11 before 5.15.210; from 5.16 before 6.1.176; from 6.2 before 6.6.143; from 6.7 before 6.12.93; from 6.13 before 6.18.35; from 6.19 before 7.0.12; 7.1; and 4 more ranges | NVD |
References
- https://git.kernel.org/stable/c/45c829e5eb3b974282bae50b7cca2cc891f74f0bpatch
- https://git.kernel.org/stable/c/e7cdcb266ba06d8480809b78ab8bb2bf8ff51ccbpatch
- https://git.kernel.org/stable/c/95f47331dfde243f93e679ce70bd0c24b37c683dpatch
- https://git.kernel.org/stable/c/d883312061ccde8c536595998aaf687ec070077cpatch
- https://git.kernel.org/stable/c/103d2de9f505f56da173e43f12dba62f92620278patch
- https://git.kernel.org/stable/c/0ca809ea8e0355299266c46e5f1755040aa8dcf3patch
- https://git.kernel.org/stable/c/7585b6aa55d8ac85ad22f522e1059f93507727b6patch
- https://git.kernel.org/stable/c/2905281cbda52ec9df540113b35b835feb5fafd3patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.