CVE-2026-80783: HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 26c45abed62536aabf4033fb6d64cf72e93374e9, 70589b0c005db003f6d8ae4db3c4d54fed7b83e4, 8a10a624996f16628234306b46f0cf36707d78bd; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 26c45abed62536aabf4033fb6d64cf72e93374e9, 70589b0c005db003f6d8ae4db3c4d54fed7b83e4, 8a10a624996f16628234306b46f0cf36707d78bd; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.37affected
- a462230e16acc8664145216da3c928d03556691a and later · before 26c45abed62536aabf4033fb6d64cf72e93374e9affected · git
- a462230e16acc8664145216da3c928d03556691a and later · before 8a10a624996f16628234306b46f0cf36707d78bdaffected · git
- a462230e16acc8664145216da3c928d03556691a and later · before d16df755b4493b6d37803c628b2c621d096796a8affected · git
- a462230e16acc8664145216da3c928d03556691a and later · before bec338b07beb883726b32192c8f01c601bc76fdaaffected · git
- a462230e16acc8664145216da3c928d03556691a and later · before 70589b0c005db003f6d8ae4db3c4d54fed7b83e4affected · git
- a462230e16acc8664145216da3c928d03556691a and later · before a33a596d3ad8dfe6c96a368097a028abeee16c17affected · git
- a462230e16acc8664145216da3c928d03556691a and later · before d095de37f78c5f32a4252ef0f99b84ba76550b86affected · git
- a462230e16acc8664145216da3c928d03556691a and later · before db8d634128d2ba88d79c0b601e983ebe14bb0519affected · git
- before 2.6.37not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.1.12-1 | 7.1.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80781Sep 4, 2026 · HID: core: fix OOB read of field->usage in hid_set_field()0Monitor
- ← EarlierCVE-2026-80782Sep 4, 2026 · HID: magicmouse: do not keep a stale msc->input if no input is claimed0Monitor
- Later →CVE-2026-80786Sep 4, 2026 · fbdev: Wrap user-invoked calls to fb_set_var() in helper0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 26c45abed62536aabf4033fb6d64cf72e93374e9 | Vendor (CNA) |
| Linux Linux | 70589b0c005db003f6d8ae4db3c4d54fed7b83e4 | Vendor (CNA) |
| Linux Linux | 8a10a624996f16628234306b46f0cf36707d78bd | Vendor (CNA) |
| Linux Linux | a33a596d3ad8dfe6c96a368097a028abeee16c17 | Vendor (CNA) |
| Linux Linux | bec338b07beb883726b32192c8f01c601bc76fda | Vendor (CNA) |
| Linux Linux | d095de37f78c5f32a4252ef0f99b84ba76550b86 | Vendor (CNA) |
| Linux Linux | d16df755b4493b6d37803c628b2c621d096796a8 | Vendor (CNA) |
| Linux Linux | db8d634128d2ba88d79c0b601e983ebe14bb0519 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/70589b0c005db003f6d8ae4db3c4d54fed7b83e4
- git.kernel.org/stable/c/8a10a624996f16628234306b46f0cf36707d78bd
- git.kernel.org/stable/c/a33a596d3ad8dfe6c96a368097a028abeee16c17
- git.kernel.org/stable/c/bec338b07beb883726b32192c8f01c601bc76fda
- git.kernel.org/stable/c/d095de37f78c5f32a4252ef0f99b84ba76550b86
- git.kernel.org/stable/c/d16df755b4493b6d37803c628b2c621d096796a8
- git.kernel.org/stable/c/db8d634128d2ba88d79c0b601e983ebe14bb0519
Vendor advisories and official records. Exploit/PoC links are deliberately left out.