CVE-2026-80783 — HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event()
In the Linux kernel, the following vulnerability has been resolved: HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event() magicmouse_raw_event() handles DOUBLE_REPORT_ID (0xf7) packets, which pack two touch reports into one, by splitting the packet and calling itself on each half. The only guard against runaway recursion is a "size < 1" check, which stops zero-sized calls but does not bound the recursion depth. A malicious HID device that matches this driver can send a report starting with DOUBLE_REPORT_ID and filled with the sequence [0xf7, 0x00]. Each level consumes two bytes and recurses on the remainder, so an incoming report of up to HID_MAX_BUFFER_SIZE (16 KiB) drives roughly 8000 nested calls. That easily exhausts the 16 KiB kernel stack, leading to a stack overflow: a panic with CONFIG_VMAP_STACK, or memory corruption without it. A double report only ever wraps two normal reports; it is never legitimately nested. Refuse to re-enter the DOUBLE_REPORT_ID case from a recursive call so the recursion depth is bounded to two, while all valid packets keep being parsed exactly as before.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
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.
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 |
≥ a462230e16acc8664145216da3c928d03556691a and < 26c45abed62536aabf4033fb6d64cf72e93374e9≥ a462230e16acc8664145216da3c928d03556691a and < 8a10a624996f16628234306b46f0cf36707d78bd≥ a462230e16acc8664145216da3c928d03556691a and < d16df755b4493b6d37803c628b2c621d096796a8≥ a462230e16acc8664145216da3c928d03556691a and < bec338b07beb883726b32192c8f01c601bc76fda≥ a462230e16acc8664145216da3c928d03556691a and < 70589b0c005db003f6d8ae4db3c4d54fed7b83e4≥ a462230e16acc8664145216da3c928d03556691a and < a33a596d3ad8dfe6c96a368097a028abeee16c17≥ a462230e16acc8664145216da3c928d03556691a and < d095de37f78c5f32a4252ef0f99b84ba76550b86≥ a462230e16acc8664145216da3c928d03556691a and < db8d634128d2ba88d79c0b601e983ebe14bb0519 and 1 moreversion 2.6.37 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 26, 2026 · 11 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.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
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
10 on the record
- git.kernel.org/stable/c/70589b0c005db003f6d8ae4db3c4d54fed7b83e4
- git.kernel.org/stable/c/d16df755b4493b6d37803c628b2c621d096796a8
- git.kernel.org/stable/c/26c45abed62536aabf4033fb6d64cf72e93374e9
- github.com/advisories/GHSA-846j-3r8r-8xv8
- git.kernel.org/stable/c/d095de37f78c5f32a4252ef0f99b84ba76550b86
- nvd.nist.gov/vuln/detail/CVE-2026-80783
- git.kernel.org/stable/c/8a10a624996f16628234306b46f0cf36707d78bd
- git.kernel.org/stable/c/db8d634128d2ba88d79c0b601e983ebe14bb0519
- git.kernel.org/stable/c/bec338b07beb883726b32192c8f01c601bc76fda
- git.kernel.org/stable/c/a33a596d3ad8dfe6c96a368097a028abeee16c17
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 23h
- Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 23h
- Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 23h
- Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 23h
- Unknown CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 23h
- Unknown CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 23h
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-80783 is "HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event()", 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.
Sign in or create an account to comment and suggest corrections.