CVE-2026-64014

published 19 Jul 2026 · updated 14 Nov 2026

Input: usbtouchscreen - clamp NEXIO data_len/x_len to URB buffer size

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e7cdcb266ba06d8480809b78ab8bb2bf8ff51ccb, Kernel 0ca809ea8e0355299266c46e5f1755040aa8dcf3, Kernel 103d2de9f505f56da173e43f12dba62f92620278 and 12 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=5197424cdcccd2b0b1922babb93969b2515c43ce <e7cdcb266ba06d8480809b78ab8bb2bf8ff51ccb, >=5197424cdcccd2b0b1922babb93969b2515c43ce <0ca809ea8e0355299266c46e5f1755040aa8dcf3, >=5197424cdcccd2b0b1922babb93969b2515c43ce <103d2de9f505f56da173e43f12dba62f92620278, >=5197424cdcccd2b0b1922babb93969b2515c43ce <2905281cbda52ec9df540113b35b835feb5fafd3, >=5197424cdcccd2b0b1922babb93969b2515c43ce <45c829e5eb3b974282bae50b7cca2cc891f74f0b, >=5197424cdcccd2b0b1922babb93969b2515c43ce <7585b6aa55d8ac85ad22f522e1059f93507727b6, >=5197424cdcccd2b0b1922babb93969b2515c43ce <95f47331dfde243f93e679ce70bd0c24b37c683d, >=5197424cdcccd2b0b1922babb93969b2515c43ce <d883312061ccde8c536595998aaf687ec070077c, =2.6.34e7cdcb266ba06d8480809b78ab8bb2bf8ff51ccb, 0ca809ea8e0355299266c46e5f1755040aa8dcf3, 103d2de9f505f56da173e43f12dba62f92620278, 2905281cbda52ec9df540113b35b835feb5fafd3, 45c829e5eb3b974282bae50b7cca2cc891f74f0b, 7585b6aa55d8ac85ad22f522e1059f93507727b6, 95f47331dfde243f93e679ce70bd0c24b37c683d, d883312061ccde8c536595998aaf687ec070077c
linux-kernel: Kernel>=5.11.0 <5.15.210, >=5.16.0 <6.1.176, >=6.13.0 <6.18.35, >=6.19.0 <7.0.12, >=6.2.0 <6.6.143, >=6.7.0 <6.12.93, >=2.6.34 <5.10.2595.15.210, 6.1.176, 6.18.35, 7.0.12, 6.6.143, 6.12.93, 5.10.259

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-64014 severity on Zeptric[![CVE-2026-64014](https://zeptric.io/badge/cve/CVE-2026-64014.svg)](https://zeptric.io/cve/CVE-2026-64014)