CVE-2026-89628Medium· 5.5▾ SunlitIn the Linux kernel, the following vulnerability has been resolved: HID: picolcd: clamp eeprom debugfs read to bytes actually received picolcd_debug_eeprom_read() trusts resp->raw_data[2] -- a length byte supplied by the device in its …
▾ Sunlit zone — Low / medium · no exploitation signal
impact 30.3 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.2%
— → 5.4
none → medium
— → 5.4
none → medium
0.2% → 0.2%
— → 5.4
none → medium
5.4 → 5.5
Last analysed / modified upstream
In the Linux kernel, the following vulnerability has been resolved:
HID: picolcd: clamp eeprom debugfs read to bytes actually received
picolcd_debug_eeprom_read() trusts resp->raw_data[2] -- a length byte supplied by the device in its REPORT_EE_DATA reply -- clamped only to the caller's read() count:
ret = resp->raw_data[2];
if (ret > s)
ret = s;
if (copy_to_user(u, resp->raw_data+3, ret))
It never checks resp->raw_size, the number of bytes picolcd_raw_event() actually copied into the 64-byte raw_data[] of the kmalloc'd struct picolcd_pending. A device (or a spoofed picoLCD) returning a length byte of 0xff, read with a count >= 255, makes copy_to_user() read past raw_data[] into adjacent slab memory and return it to userspace through the debugfs "eeprom" file:
BUG: KASAN: slab-out-of-bounds in _copy_to_user
Read of size 255 ... picolcd_debug_eeprom_read+0x214/0x2f0 [hid_picolcd]
The debug-dump path in the same file already validates the device length byte against the received size before trusting it; this read does not. The file is created S_IRUSR (root-only) and a crafted device is needed, so it is neither unprivileged- nor remotely-triggerable.
Clamp the copy length to resp->raw_size - 3 (the payload actually received, minus the 3-byte header), floored at 0 for short replies.
Linux >= 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba < 1a02056c2bf7ef9b5fd05ee6913aeeadb703c443Linux >= 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba < 65daa322f1021d8206f8032c4cd4c0cb2d26c7c3Linux >= 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba < 8dc662af019158690c470edd2e2857657f700abbLinux >= 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba < 4daf432c94a42e7be6aa10b012b33af5ed9bc118Linux >= 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba < a3e6e8d7198a9f3861861520a38b673684a1062bLinux >= 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba < 471f4a939c66d1d44aece2321807abf609fc9098Linux >= 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba < 699a3c8b56e168ca19d12722f3f5ef1d6f4b1d84Linux >= 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba < e9c667395ac1f8024f623250b32bae4c7af9caa0Linux 2.6.35Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Field changes observed since this record was first indexed.
Connected by shared product, vendor, weakness, or advisory.
CVE-2024-57804High· 7.3scsi: mpi3mr: Fix corrupt config pages PHY state is switched in sysfs
CVE-2024-47794High· 7.8bpf: Prevent tailcall infinite loop caused by freplace
CVE-2026-100070Medium· 5.5In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_nat_sip: rewind offset when NAT shrinks the packet sashiko says: If map_addr() changes the packet length, such as when the public NAT IP string is shor…
CVE-2026-100071Medium· 5.5In the Linux kernel, the following vulnerability has been resolved: net: hsr: free learned nodes on device setup failure hsr_dev_finalize() can fail after a lower-device RX handler has already been registered (slave A is added before t…
CVE-2025-39977High· 7.8In the Linux kernel, the following vulnerability has been resolved: futex: Prevent use-after-free during requeue-PI syzbot managed to trigger the following race: T1 T2 futex_wait_requeue_pi() fute…
CVE-2026-99100Nonewifi: p54: validate firmware record lengths