Unknown

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

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.

Published Oct 18, 2026 · Updated Oct 18, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

No scoring signals.

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ 4f4001bc76fd1a138a501fbd3d68cce72cbf96ce and < 1f1bd9a3117f082eb891c0986c4f0e04cd974c9a≥ 4f4001bc76fd1a138a501fbd3d68cce72cbf96ce and < 0c19a6c1d25fd5ed66d1f80dc6f6e56cc1f0a787≥ 4f4001bc76fd1a138a501fbd3d68cce72cbf96ce and < a0125ca86e405b8a704e96157a6c10ca51087652≥ 4f4001bc76fd1a138a501fbd3d68cce72cbf96ce and < 5acb2dace582f061aab5e14c399ac9480315f44bversion 4.13	Vulnerable	CVE Program (cve.org) e CISA ADP

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 18, 2026
Affected products added · linux/linux
Oct 18, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 18, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 18, 2026 · NIST National Vulnerability Database
CVE published
Oct 18, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 18, 2026 – Oct 18, 2026

References

4 on the record

git.kernel.org/stable/c/0c19a6c1d25fd5ed66d1f80dc6f6e56cc1f0a787
NIST National Vulnerability Database
git.kernel.org/stable/c/5acb2dace582f061aab5e14c399ac9480315f44b
NIST National Vulnerability Database
git.kernel.org/stable/c/1f1bd9a3117f082eb891c0986c4f0e04cd974c9a
NIST National Vulnerability Database
git.kernel.org/stable/c/a0125ca86e405b8a704e96157a6c10ca51087652
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 9h
Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 9h
Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 9h
Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 9h
Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 9h
Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 9h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-98859 is "HID: multitouch: stop the release timer from being rearmed on remove", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.