CVE-2026-80782: Linux kernel · HID: magicmouse: do not keep a stale msc->input if no input is claimed
Source GCVE Database
Not known to be exploited.
Data as of 26 Oct 2026, 14:05 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
Description
In the Linux kernel, the following vulnerability has been resolved: HID: magicmouse: do not keep a stale msc->input if no input is claimed magicmouse_input_mapping() caches the first hid_input's input_dev in msc->input while the report descriptor is parsed, and the rest of the driver treats a non-NULL msc->input as proof that an input device was registered. That does not hold on the hid-input error path. If hidinput_connect() fails -- for instance because input_register_device() returns an error -- it unwinds through hidinput_disconnect(), which frees every input_dev it created, including the one cached in msc->input. The failure does not abort the probe. hid_connect() only skips the claim: if ((connect_mask & HID_CONNECT_HIDINPUT) && !hidinput_connect(hdev, connect_mask & HID_CONNECT_HIDINPUT_FORCE)) hdev->claimed |= HID_CLAIMED_INPUT; and the "device has no listeners" bailout below it does not fire for this driver, which sets ->raw_event; on the USB Magic Mouse 2 / Magic Trackpad 2 paths hidraw and hiddev are claimed as well. hid_hw_start() therefore returns 0 and magicmouse_probe() continues with msc->input pointing at freed memory. Being non-NULL, it passes the "input not registered" check in probe and the NULL checks in ->raw_event and ->event, so the next input report dereferences freed memory. Clear msc->input when the HID core did not claim an input device, so the existing NULL checks cover this case as well.
References
- nvd.nist.gov/vuln/detail/CVE-2026-80782 (opens in a new tab)
- git.kernel.org/stable/c/0af3b89705688af01aa06025b84fa7a1e06ba6cc (opens in a new tab)
- git.kernel.org/stable/c/0bf253e9ac994cb5329bc87b00bb4eeca9136791 (opens in a new tab)
- git.kernel.org/stable/c/15b60ade825c8ce9ec560048a4ae3747e4572be3 (opens in a new tab)
- git.kernel.org/stable/c/2ef16934e069d5f771e989d6ee5c3ece5042f3cd (opens in a new tab)
- git.kernel.org/stable/c/3d7a7bac4c75f25b2513505a0ac5ba909588ed2b (opens in a new tab)
- git.kernel.org/stable/c/403cc9bd6ccb9fbe68d501c3236e5a6dd5504e14 (opens in a new tab)
- git.kernel.org/stable/c/9bdf8c7bfd79f1090e61d28f969b32880fd77bb3 (opens in a new tab)
- git.kernel.org/stable/c/c3597923932bb90d4fc2186aef552f6677175e4a (opens in a new tab)
- git.kernel.org/stable/c/e0c224c93d10ee38854fdf24c815108aedd3dcb3 (opens in a new tab)