Cloudanix VulnDB

CVE-2026-80783

None

CVSS

—

EPSS

0.2%

Published

Sep 4, 2026

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A specially crafted computer mouse can make the system crash by overwhelming its internal memory handling.

Exploitation
Physical Access
Attacker needs
Physical Access
Complexity
Moderate
Impact
Denial Of Service
Component
OS kernel
Class
Memory Corruption
Remediation
Patch
Effort
Low
Patch risk
Low

What it actually does

The flaw permits a malicious HID device to send DOUBLE_REPORT_ID (0xf7) packets that trigger unbounded recursion in magicmouse_raw_event(), consuming up to roughly 8000 nested calls and exhausting the 16 KiB kernel stack, resulting in panic or memory corruption.

Why it matters to the business

Linux systems with the magicmouse driver may experience sudden kernel crashes or corruption when a crafted HID device is connected, causing downtime and potential data loss on affected hardware.

How an attack unfolds

An attacker presents a malicious HID device matching the magicmouse driver and sends a report beginning with DOUBLE_REPORT_ID followed by repeated [0xf7, 0x00] sequences; each recursive call strips two bytes and re-invokes the handler until the stack overflows.

How to fix it

Apply the upstream fix that refuses re-entry into the DOUBLE_REPORT_ID case from recursive calls, bounding depth to two while preserving normal parsing; rebuild and deploy the patched kernel on all affected systems.

How to confirm the fix worked

Confirm the patch is present by inspecting magicmouse_raw_event() for the added recursion guard and test with a synthetic DOUBLE_REPORT_ID packet that previously triggered deep recursion.

Typical attack path

  1. Connect a malicious HID device recognized by the magicmouse driver
  2. Transmit a DOUBLE_REPORT_ID packet containing the recursive sequence
  3. Trigger repeated self-calls during packet splitting
  4. Exhaust kernel stack leading to overflow

How to detect it

Search kernel logs and crash dumps for magicmouse_raw_event stack overflows or panics on systems with CONFIG_VMAP_STACK; correlate with recent HID device connections.

What your security team should do

  • Prioritize kernel updates containing the recursion bound on all Linux hosts using HID input devices
  • Disable the magicmouse driver via module blacklist if the hardware is not required
  • Monitor kernel logs for stack-overflow panics referencing magicmouse_raw_event

The record

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 packages

Ecosystem Package Introduced Fixed