{"id":"CVE-2026-98859","summary":"HID: multitouch: stop the release timer from being rearmed on remove","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nHID: multitouch: stop the release timer from being rearmed on remove\n\nmt_remove() quiesces the sticky-finger timer before stopping the\nhardware:\n\n    timer_delete_sync(&td-\u003erelease_timer);\n\n    sysfs_remove_group(&hdev-\u003edev.kobj, &mt_attribute_group);\n    hid_hw_stop(hdev);\n\ntimer_delete_sync() waits for a running callback and dequeues the timer,\nbut it does not stop the timer from being armed again. The transport is\nstill delivering reports at that point, and the report path rearms it:\n\n    if (app-\u003equirks & MT_QUIRK_STICKY_FINGERS) {\n        if (td-\u003emt_io_flags & MT_IO_SLOTS_MASK)\n            mod_timer(&td-\u003erelease_timer,\n                      jiffies + msecs_to_jiffies(100));\n\nA report that arrives after timer_delete_sync() has returned therefore\nleaves the timer queued. td is allocated with devm_kzalloc() against\nhdev-\u003edev, so it is freed when the driver is unbound, after mt_remove()\nreturns. When the timer fires afterwards, mt_expired_timeout()\ndereferences the freed td:\n\n    struct mt_device *td = timer_container_of(td, t, release_timer);\n    struct hid_device *hdev = td-\u003ehdev;\n\n    if (test_and_set_bit_lock(MT_IO_FLAGS_RUNNING, &td-\u003emt_io_flags))\n\nSimply moving the teardown after hid_hw_stop() does not fix this on its\nown, because mt_expired_timeout() calls mt_release_contacts(), which\nwalks hdev-\u003einputs; the timer still has to be quiesced before\nhid_hw_stop() tears the input devices down.\n\nUse timer_shutdown_sync() instead, which additionally makes any later\nmod_timer() a no-op, so neither ordering constraint has to be traded off\nagainst the other. This is the final-teardown pattern the function was\nintroduced for, and hid-wiimote already uses it for the same reason.","modified":"2026-10-19T02:46:05.849709503Z","published":"2026-10-18T15:51:20.456Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98859.json"},"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/0c19a6c1d25fd5ed66d1f80dc6f6e56cc1f0a787"},{"type":"WEB","url":"https://git.kernel.org/stable/c/1f1bd9a3117f082eb891c0986c4f0e04cd974c9a"},{"type":"WEB","url":"https://git.kernel.org/stable/c/5acb2dace582f061aab5e14c399ac9480315f44b"},{"type":"WEB","url":"https://git.kernel.org/stable/c/a0125ca86e405b8a704e96157a6c10ca51087652"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98859.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98859"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"4f4001bc76fd1a138a501fbd3d68cce72cbf96ce"},{"fixed":"1f1bd9a3117f082eb891c0986c4f0e04cd974c9a"},{"fixed":"0c19a6c1d25fd5ed66d1f80dc6f6e56cc1f0a787"},{"fixed":"a0125ca86e405b8a704e96157a6c10ca51087652"},{"fixed":"5acb2dace582f061aab5e14c399ac9480315f44b"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98859.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.13.0"},{"fixed":"6.12.113"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.56"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.2.10"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98859.json"}}],"schema_version":"1.9.0"}