Heimdall Security Logo

CVE-2026-64364

Vulnérabilité élevée dans Linux (Linux)

CVSS 8.8 · Élevée
EPSS 0.4%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 6.18.39, <5.15.212, 77711d850bed75ae7142c3d1f22c1a8b4d049c33, 6acfe25968913788d30ec0eedd80178c4ea3f1d0, 0, <37daa8c96bd563d03150e23f094cb60703594a6d, <=7.1.*, 7.1.4, <152983d87387f6a8ae72b73474cfa55fbcf1ec75, 6.6.114, 6.18, 6.1.178, <=5.10.*, <=6.6.*, 6.12.97, <12e90656e330ff8bbaf2f29c535fdb8a11cc6f55, <6.1.178, <a6d5ce2e1a2d7bf189bde8a659d04b65f0b0725d, <8813b0612275cc61fe9e6603d0ee019247ade6be, <6493ebf9489efef0105078377b973ab33d51af22, f32fea4c0234c971c12e46d76612cdc2dd4bb046, <=6.18.*, 5.15.212, d280c138e66be87d1fccfed42593f02fdb893905, 6.6.145, 5.10.261, 46f781e0d151844589dc2125c8cce3300546f92a, 6.1.158, 5.10.246, <5.10.261, <6.18, <6.6.145, fc488f675344931ffab6a51c43691065ec006567, <b5c037d6b807017e74a115288f81bc9cd5a5aab8, <=*, <=5.15.*, <6.12.97, 5.15.196, 7.2, 59bd04163e6451b9c7275277882ed9f4abfa2051, 6.17.5, <e24918ee67c4dc3d20d4670750e46e9b160365f4, 6.12.55

Description

In the Linux kernel, the following vulnerability has been resolved: HID: multitouch: fix out-of-bounds bit access on mt_io_flags mt_io_flags is a single unsigned long, but mt_process_slot(), mt_release_pending_palms() and mt_release_contacts() use it as a per-slot bitmap indexed by the slot number. That slot number is only bounded by td->maxcontacts, which is taken from the device's ContactCountMaximum feature report and can be up to 255, not by BITS_PER_LONG. As a result, a multitouch device that advertises a large contact count makes set_bit()/clear_bit() operate past the mt_io_flags word and corrupt the adjacent members of struct mt_device. The sticky-fingers release timer is the easiest way to reach this. mt_release_contacts() runs for (i = 0; i < mt->num_slots; i++) clear_bit(i, &td->mt_io_flags); with num_slots == maxcontacts. For maxcontacts around 250 the loop clears the bits that overlap td->applications.next, zeroing that list head, and the list_for_each_entry() that immediately follows then dereferences NULL. The kernel panics from timer (softirq) context. On a KASAN build this shows up as a general protection fault in mt_release_contacts() with a null-ptr-deref at offset 0x58, which is offsetof(struct mt_application, num_received). The state is reachable from an untrusted USB or Bluetooth HID multitouch device; no local privileges are required. Store the per-slot active state in a separately allocated bitmap sized for maxcontacts, the same pattern already used for pending_palm_slots, and keep only MT_IO_FLAGS_RUNNING in mt_io_flags. The two "mt_io_flags & MT_IO_SLOTS_MASK" arming checks become bitmap_empty(td->active_slots, td->maxcontacts). Move MT_IO_FLAGS_RUNNING back to bit 0. It was bumped to bit 32 by the same commit to leave the low byte for the slot bits; with the slot bits gone it fits in bit 0 again, which also keeps it within the unsigned long on 32-bit.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 6.18.39, <5.15.212, 77711d850bed75ae7142c3d1f22c1a8b4d049c33, 6acfe25968913788d30ec0eedd80178c4ea3f1d0, 0, <37daa8c96bd563d03150e23f094cb60703594a6d, <=7.1.*, 7.1.4, <152983d87387f6a8ae72b73474cfa55fbcf1ec75, 6.6.114, 6.18, 6.1.178, <=5.10.*, <=6.6.*, 6.12.97, <12e90656e330ff8bbaf2f29c535fdb8a11cc6f55, <6.1.178, <a6d5ce2e1a2d7bf189bde8a659d04b65f0b0725d, <8813b0612275cc61fe9e6603d0ee019247ade6be, <6493ebf9489efef0105078377b973ab33d51af22, f32fea4c0234c971c12e46d76612cdc2dd4bb046, <=6.18.*, 5.15.212, d280c138e66be87d1fccfed42593f02fdb893905, 6.6.145, 5.10.261, 46f781e0d151844589dc2125c8cce3300546f92a, 6.1.158, 5.10.246, <5.10.261, <6.18, <6.6.145, fc488f675344931ffab6a51c43691065ec006567, <b5c037d6b807017e74a115288f81bc9cd5a5aab8, <=*, <=5.15.*, <6.12.97, 5.15.196, 7.2, 59bd04163e6451b9c7275277882ed9f4abfa2051, 6.17.5, <e24918ee67c4dc3d20d4670750e46e9b160365f4, 6.12.55) 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