{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98859 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98859 is an use after free vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98859 and fix it if it is affected.\n\nWhat it is: CVE-2026-98859 is an use after free vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98859 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98859/ (Markdown: https://insights.sbomify.com/CVE-2026-98859/index.md)","id":"CVE-2026-98859","markdown":"https://insights.sbomify.com/CVE-2026-98859/index.md","name":"CVE-2026-98859","record":{"aliases":["AZL-108818","BELL-CVE-2026-98859","DEBIAN-CVE-2026-98859","GHSA-rf84-p87x-87h6","UBUNTU-CVE-2026-98859"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A use-after-free vulnerability in the Linux kernel HID multitouch driver allows local attackers to cause a system crash or potentially execute code via a race condition during device removal.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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(\u0026td-\u003erelease_timer);\n\n    sysfs_remove_group(\u0026hdev-\u003edev.kobj, \u0026mt_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 \u0026 MT_QUIRK_STICKY_FINGERS) {\n        if (td-\u003emt_io_flags \u0026 MT_IO_SLOTS_MASK)\n            mod_timer(\u0026td-\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, \u0026td-\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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"HID: multitouch: stop the release timer from being rearmed on remove","id":"CVE-2026-98859","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"HID: bpf: cast size to ssize_t when checking hid_bpf_hw_request","id":"CVE-2026-98860"},"packages":[],"prev":{"headline":"io_uring: fix task_work add use-after-free with SQPOLL","id":"CVE-2026-98858"},"products":["Linux"],"published":"2026-10-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A use-after-free vulnerability in the Linux kernel HID multitouch driver allows local attackers to cause a system crash or potentially execute code via a race condition during device removal.","url":"https://insights.sbomify.com/CVE-2026-98859/"}