Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89628

HID: picolcd: clamp eeprom debugfs read to bytes actually received

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba – < 1a02056c2bf7ef9b5fd05ee6913aeeadb703c443
    • affected 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba – < 65daa322f1021d8206f8032c4cd4c0cb2d26c7c3
    • affected 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba – < 8dc662af019158690c470edd2e2857657f700abb
    • affected 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba – < 4daf432c94a42e7be6aa10b012b33af5ed9bc118
    • affected 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba – < a3e6e8d7198a9f3861861520a38b673684a1062b
    • affected 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba – < 471f4a939c66d1d44aece2321807abf609fc9098
    • affected 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba – < 699a3c8b56e168ca19d12722f3f5ef1d6f4b1d84
    • affected 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba – < e9c667395ac1f8024f623250b32bae4c7af9caa0
  • Linux · Linux

    • affected 2.6.35
    • unaffected < 2.6.35
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89628 badge
[![CVE-2026-89628](https://cveledger.app/badge/CVE-2026-89628.svg)](https://cveledger.app/cve/CVE-2026-89628)

Record last updated .