CVE-2026-80783

HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event()

N/A
Published: September 4, 2026 at 03:12 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.37a462230e16acc8664145216da3c928d03556691a
Vendor states this is fixed in 26c45abed62536aabf4033fb6d64cf72e93374e9 (fixed)
Vendor states this is fixed in 70589b0c005db003f6d8ae4db3c4d54fed7b83e4 (fixed)
Vendor states this is fixed in 8a10a624996f16628234306b46f0cf36707d78bd (fixed)
Vendor states this is fixed in a33a596d3ad8dfe6c96a368097a028abeee16c17 (fixed)
Vendor states this is fixed in bec338b07beb883726b32192c8f01c601bc76fda (fixed)
Vendor states this is fixed in d095de37f78c5f32a4252ef0f99b84ba76550b86 (fixed)
Vendor states this is fixed in d16df755b4493b6d37803c628b2c621d096796a8 (fixed)
Vendor states this is fixed in db8d634128d2ba88d79c0b601e983ebe14bb0519 (fixed)
Vendor states this is fixed in 2.6.37 (unaffected)
Vendor states this is fixed in 5.15.220 (unaffected)
Vendor states this is fixed in 6.1.187 (unaffected)
Vendor states this is fixed in 6.12.108 (unaffected)
Vendor states this is fixed in 6.18.49 (unaffected)
Vendor states this is fixed in 6.6.156 (unaffected)
Vendor states this is fixed in 7.1.11 (unaffected)
Vendor states this is fixed in 7.2.1 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card