CVE-2026-64364
Last modified
CVE-2026-64364 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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. EPSS estimates a 0.35% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.10.246, < 5.10.261 | — |
| Linux | Linux Kernel | >= 5.15.196, < 5.15.212 | — |
| Linux | Linux Kernel | >= 6.1.158, < 6.1.178 | — |
| Linux | Linux Kernel | >= 6.6.114, < 6.6.145 | — |
| Linux | Linux Kernel | >= 6.12.55, < 6.12.97 | — |
| Linux | Linux Kernel | >= 6.17.5, < 6.18 | — |
| Linux | Linux Kernel | >= 6.18.1, < 6.18.39 | — |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 | — |
| Linux | Linux Kernel | 6.18 | — |
| Linux | Linux Kernel | 7.2 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64364?
How severe is CVE-2026-64364?
How do I fix CVE-2026-64364?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64358In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64359In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64360In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64361In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64362In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64363In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64365In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64366In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64367In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64368In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-64369In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-6437Improper neutralization of argument delimiters in the volume…6.9
Are you affected by CVE-2026-64364?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
