CVE-2026-64014
CVE CVE-2026-64014EUVD EUVD-2026-45587Published 2026-07-19T14:56:27.000Z
What the advisory describes
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: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 5.10.259; 5197424cdcccd2b0b1922babb93969b2515c43ce <7585b6aa55d8ac85ad22f522e1059f93507727b6; patch: 6.1.176; 5197424cdcccd2b0b1922babb93969b2515c43ce <95f47331dfde243f93e679ce70bd0c24b37c683d; 5197424cdcccd2b0b1922babb93969b2515c43ce <e7cdcb266ba06d8480809b78ab8bb2bf8ff51ccb; 5197424cdcccd2b0b1922babb93969b2515c43ce <2905281cbda52ec9df540113b35b835feb5fafd3; patch: 0; patch: 6.6.143; 5197424cdcccd2b0b1922babb93969b2515c43ce <d883312061ccde8c536595998aaf687ec070077c; 5197424cdcccd2b0b1922babb93969b2515c43ce <103d2de9f505f56da173e43f12dba62f92620278; patch: 6.18.35; patch: 6.12.93; 5197424cdcccd2b0b1922babb93969b2515c43ce <0ca809ea8e0355299266c46e5f1755040aa8dcf3; patch: 5.15.210; 5197424cdcccd2b0b1922babb93969b2515c43ce <45c829e5eb3b974282bae50b7cca2cc891f74f0b; patch: 7.1; patch: 7.0.12; 2.6.34
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.