Heimdall Security Logo

CVE-2026-89628

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <4daf432c94a42e7be6aa10b012b33af5ed9bc118, <8dc662af019158690c470edd2e2857657f700abb, 5.15.221, 5.10.270, 0, 7.2.4, 6.1.188, 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba, <e9c667395ac1f8024f623250b32bae4c7af9caa0, <=5.10.*, <=6.6.*, <a3e6e8d7198a9f3861861520a38b673684a1062b, 6.6.157, <=6.18.*, <471f4a939c66d1d44aece2321807abf609fc9098, <65daa322f1021d8206f8032c4cd4c0cb2d26c7c3, <2.6.35, <=7.2.*, <699a3c8b56e168ca19d12722f3f5ef1d6f4b1d84, <=*, <=5.15.*, 6.18.50, <1a02056c2bf7ef9b5fd05ee6913aeeadb703c443, 6.12.109, 2.6.35, 7.3

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.

Gravité et risque d'exploitation

CVE-2026-89628 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.22 %, ce qui la place devant 11.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <4daf432c94a42e7be6aa10b012b33af5ed9bc118, <8dc662af019158690c470edd2e2857657f700abb, 5.15.221, 5.10.270, 0, 7.2.4, 6.1.188, 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba, <e9c667395ac1f8024f623250b32bae4c7af9caa0, <=5.10.*, <=6.6.*, <a3e6e8d7198a9f3861861520a38b673684a1062b, 6.6.157, <=6.18.*, <471f4a939c66d1d44aece2321807abf609fc9098, <65daa322f1021d8206f8032c4cd4c0cb2d26c7c3, <2.6.35, <=7.2.*, <699a3c8b56e168ca19d12722f3f5ef1d6f4b1d84, <=*, <=5.15.*, 6.18.50, <1a02056c2bf7ef9b5fd05ee6913aeeadb703c443, 6.12.109, 2.6.35, 7.3) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE