CVE-2026-89623

HID: mcp2221: stop device IO before hid_hw_stop

N/A
Published: September 11, 2026 at 07:45 PM UTC
Updated: October 24, 2026 at 03:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: HID: mcp2221: stop device IO before hid_hw_stop Quiesce device IO at the start of the devm cleanup callback mcp2221_hid_unregister() so that incoming HID reports cannot race with hardware teardown during probe failure or device removal, addressing a potential use-after-free. Guard the call to hid_device_io_stop() with io_started. On normal removal hid_device_remove() has already cleared io_started before the devres group is released, so an unconditional call would otherwise hit the !io_started path and emit a spurious "io already stopped" warning on every removal. The guard preserves the probe-failure balancing, where io_started is still set after hid_device_io_start(), while staying silent on the normal removal path.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.6.86.773ce9f1f2741a38f5d27393e627702ae2c46e6f2d4b50ac06ea6e47bdd2b04e97d1090c673c80645
Vendor states this is fixed in 0ae90a19e6b5a8557d25d95facb7e01c9c07af38 (fixed)
Vendor states this is fixed in 2eda1513f573945c1e3a0090341f3d28740463b1 (fixed)
Vendor states this is fixed in 85d963499f1feeea287c0a37c3eac3fc1898eca9 (fixed)
Vendor states this is fixed in c99ba6c234d4d537c317336376b78c088174034a (fixed)
Vendor states this is fixed in dca151633c0fde90935311c60e7cfc064aa56134 (fixed)
Affected range stops below 6.12.109, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.12.109 (unaffected)
Affected range stops below 6.18.50, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.18.50 (unaffected)
Affected range stops below 6.6.157, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.157 (unaffected)
Affected range stops below 7.2.4, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Affected range stops below 7.3-rc1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card