CVE-2026-89628

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 11, 2026

Last Modified

September 14, 2026

References (8)

Vendor Advisories for CVE-2026-89628(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 13× in last 7d / 50× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 56 is merged into the row it repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-12 14:48 UTCEG score recompute
  4. 2026-10-11 19:15 UTCEG score recompute
  5. 2026-10-11 16:31 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-11 13:47 UTCEG score recompute
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-10 11:04 UTCVendor advisory
  10. 2026-10-10 11:04 UTCGHSA enrichmentGHSA-84x9-cxq8-hpgq
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  14. 2026-10-07 05:36 UTCVendor advisory
  15. 2026-10-07 05:36 UTCGHSA enrichmentGHSA-84x9-cxq8-hpgq
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-10-04 00:09 UTCVendor advisory
  20. 2026-10-04 00:09 UTCGHSA enrichmentGHSA-84x9-cxq8-hpgq
  21. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  22. 2026-09-30 18:19 UTCEG score recompute
  23. 2026-09-30 18:19 UTCGHSA enrichmentGHSA-84x9-cxq8-hpgq
  24. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 11th percentile
Show 30 more
  1. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-09-27 12:19 UTCVendor advisory
  3. 2026-09-27 12:19 UTCGHSA enrichmentGHSA-84x9-cxq8-hpgq
  4. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-09-24 06:51 UTCVendor advisory
  7. 2026-09-24 06:51 UTCGHSA enrichmentGHSA-84x9-cxq8-hpgq
  8. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  11. 2026-09-21 01:24 UTCVendor advisory
  12. 2026-09-21 01:24 UTCGHSA enrichmentGHSA-84x9-cxq8-hpgq
  13. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  14. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  15. 2026-09-17 19:38 UTCVendor advisory
  16. 2026-09-17 19:38 UTCGHSA enrichmentGHSA-84x9-cxq8-hpgq
  17. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  18. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  19. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  20. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-09-14 13:31 UTCGHSA enrichmentGHSA-84x9-cxq8-hpgq
  22. 2026-09-14 13:28 UTCNVD update
  23. 2026-09-14 12:28 UTCEG score recompute
  24. 2026-09-14 12:28 UTCGHSA enrichmentGHSA-84x9-cxq8-hpgq
  25. 2026-09-14 12:24 UTCMITRE cvelistV5
  26. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  27. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  28. 2026-09-11 20:36 UTCNVD update
  29. 2026-09-11 19:49 UTCEG score recompute
  30. 2026-09-11 19:49 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-89628?
CVE-2026-89628 is a vulnerability whose severity is not yet rated; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: HID: picolcd: clamp eeprom debugfs read to bytes actually received picolcddebugeepromread() trusts resp->rawdata[2] -- a length byte supplied by the device in its REPORTEEDATA reply -- clamped only to the caller's read() count: ret…
When was the CVE record for CVE-2026-89628 published?
The CVE record for CVE-2026-89628 was published on September 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 14, 2026; the record at its source may have been updated since.
Is CVE-2026-89628 actively exploited?
CVE-2026-89628 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-89628?
A fix for CVE-2026-89628 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89628 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-89628

Explore →

Is Your Infrastructure Affected by CVE-2026-89628?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs