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-64364HID: multitouch: fix out-of-bounds bit access on mt_io_flags

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months 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

CVSS scores of CVE-2026-64364, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.36% · top 70% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected fc488f675344931ffab6a51c43691065ec006567 – < 12e90656e330ff8bbaf2f29c535fdb8a11cc6f55
    • affected 77711d850bed75ae7142c3d1f22c1a8b4d049c33 – < 152983d87387f6a8ae72b73474cfa55fbcf1ec75
    • affected 6acfe25968913788d30ec0eedd80178c4ea3f1d0 – < b5c037d6b807017e74a115288f81bc9cd5a5aab8
    • affected d280c138e66be87d1fccfed42593f02fdb893905 – < a6d5ce2e1a2d7bf189bde8a659d04b65f0b0725d
    • affected f32fea4c0234c971c12e46d76612cdc2dd4bb046 – < e24918ee67c4dc3d20d4670750e46e9b160365f4
    • affected 46f781e0d151844589dc2125c8cce3300546f92a – < 37daa8c96bd563d03150e23f094cb60703594a6d
    • affected 46f781e0d151844589dc2125c8cce3300546f92a – < 6493ebf9489efef0105078377b973ab33d51af22
    • affected 46f781e0d151844589dc2125c8cce3300546f92a – < 8813b0612275cc61fe9e6603d0ee019247ade6be
    • affected 59bd04163e6451b9c7275277882ed9f4abfa2051
    • affected 5.10.246 – < 5.10.261
    • affected 5.15.196 – < 5.15.212
    • affected 6.1.158 – < 6.1.178
    • affected 6.6.114 – < 6.6.145
    • affected 6.12.55 – < 6.12.97
    • affected 6.17.5 – < 6.18
  • Linux · Linux

    • affected 6.18
    • unaffected < 6.18
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .