Unknown

CVE-2026-80782 — HID: magicmouse: do not keep a stale msc->input if no input is claimed

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.

Published Sep 4, 2026 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · 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

EPSS 0.2% (30-day exploitation probability)+1

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

0.2%

ahead of 9% of scored CVEs · Oct 27, 2026

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	≥ f1a9a149abc86903e81dd1b2e720f3f89874384b and < c3597923932bb90d4fc2186aef552f6677175e4a≥ f1a9a149abc86903e81dd1b2e720f3f89874384b and < e0c224c93d10ee38854fdf24c815108aedd3dcb3≥ f1a9a149abc86903e81dd1b2e720f3f89874384b and < 403cc9bd6ccb9fbe68d501c3236e5a6dd5504e14≥ f1a9a149abc86903e81dd1b2e720f3f89874384b and < 3d7a7bac4c75f25b2513505a0ac5ba909588ed2b≥ f1a9a149abc86903e81dd1b2e720f3f89874384b and < 9bdf8c7bfd79f1090e61d28f969b32880fd77bb3≥ f1a9a149abc86903e81dd1b2e720f3f89874384b and < 15b60ade825c8ce9ec560048a4ae3747e4572be3≥ f1a9a149abc86903e81dd1b2e720f3f89874384b and < 0bf253e9ac994cb5329bc87b00bb4eeca9136791≥ f1a9a149abc86903e81dd1b2e720f3f89874384b and < 2ef16934e069d5f771e989d6ee5c3ece5042f3cd and 4 more ≥ f1a9a149abc86903e81dd1b2e720f3f89874384b and < 0af3b89705688af01aa06025b84fa7a1e06ba6ccversion 0e55072e7c63a6569cab1447e9025d160abd9dd9≥ 3.8.7 and < 3.9version 3.9	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 27, 2026 · 12 reading(s) · max 0.20%

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 15, 2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 4, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 19, 2026 – Oct 19, 2026
1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

11 on the record

git.kernel.org/stable/c/0af3b89705688af01aa06025b84fa7a1e06ba6cc
NIST National Vulnerability Database
git.kernel.org/stable/c/9bdf8c7bfd79f1090e61d28f969b32880fd77bb3
NIST National Vulnerability Database
github.com/advisories/GHSA-43vj-4w6q-2r6j
GitHub Security Advisories
git.kernel.org/stable/c/c3597923932bb90d4fc2186aef552f6677175e4a
NIST National Vulnerability Database
nvd.nist.gov/vuln/detail/CVE-2026-80782
GitHub Security Advisories
git.kernel.org/stable/c/403cc9bd6ccb9fbe68d501c3236e5a6dd5504e14
NIST National Vulnerability Database
git.kernel.org/stable/c/3d7a7bac4c75f25b2513505a0ac5ba909588ed2b
NIST National Vulnerability Database
git.kernel.org/stable/c/2ef16934e069d5f771e989d6ee5c3ece5042f3cd
NIST National Vulnerability Database
git.kernel.org/stable/c/0bf253e9ac994cb5329bc87b00bb4eeca9136791
NIST National Vulnerability Database
git.kernel.org/stable/c/15b60ade825c8ce9ec560048a4ae3747e4572be3
NIST National Vulnerability Database
git.kernel.org/stable/c/e0c224c93d10ee38854fdf24c815108aedd3dcb3
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 3h
Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 3h
Unknown CVE-2026-99214 drm/vc4: hdmi: Move packet RAM enable to PM runtime 3h
Unknown CVE-2026-99213 vsock: treat TCP_CLOSING as once-established 3h
Unknown CVE-2026-99212 net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure 3h
Unknown CVE-2026-99211 netlink: reset skb headers before unicast and multicast filtering 3h

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 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-80782 is "HID: magicmouse: do not keep a stale msc->input if no input is claimed", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. 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.