GHSA-P59V-M859-4PPQ
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-14 15:32In 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": [],
"aliases": [
"CVE-2026-89623"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:19:47Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nHID: mcp2221: stop device IO before hid_hw_stop\n\nQuiesce device IO at the start of the devm cleanup callback\nmcp2221_hid_unregister() so that incoming HID reports cannot race with\nhardware teardown during probe failure or device removal, addressing a\npotential use-after-free.\n\nGuard the call to hid_device_io_stop() with io_started. On normal\nremoval hid_device_remove() has already cleared io_started before the\ndevres group is released, so an unconditional call would otherwise hit\nthe !io_started path and emit a spurious \"io already stopped\" warning\non every removal. The guard preserves the probe-failure balancing,\nwhere io_started is still set after hid_device_io_start(), while\nstaying silent on the normal removal path.",
"id": "GHSA-p59v-m859-4ppq",
"modified": "2026-09-14T15:32:32Z",
"published": "2026-09-11T21:31:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89623"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0ae90a19e6b5a8557d25d95facb7e01c9c07af38"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2eda1513f573945c1e3a0090341f3d28740463b1"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/85d963499f1feeea287c0a37c3eac3fc1898eca9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c99ba6c234d4d537c317336376b78c088174034a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/dca151633c0fde90935311c60e7cfc064aa56134"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.