CVE-2026-80783 Affecting linux-6.12 package, versions <6.12.111-1~deb12u1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN12-LINUX612-20506484
- published5 Oct 2026
- disclosed4 Sept 2026
Introduced: 4 Sep 2026
CVE-2026-80783 (opens in a new tab)How to fix?
Upgrade Debian:12 linux-6.12 to version 6.12.111-1~deb12u1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream linux-6.12 package and not the linux-6.12 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
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.
References
- https://security-tracker.debian.org/tracker/CVE-2026-80783
- https://git.kernel.org/stable/c/26c45abed62536aabf4033fb6d64cf72e93374e9
- https://git.kernel.org/stable/c/70589b0c005db003f6d8ae4db3c4d54fed7b83e4
- https://git.kernel.org/stable/c/8a10a624996f16628234306b46f0cf36707d78bd
- https://git.kernel.org/stable/c/a33a596d3ad8dfe6c96a368097a028abeee16c17
- https://git.kernel.org/stable/c/bec338b07beb883726b32192c8f01c601bc76fda
- https://git.kernel.org/stable/c/d095de37f78c5f32a4252ef0f99b84ba76550b86
- https://git.kernel.org/stable/c/d16df755b4493b6d37803c628b2c621d096796a8
- https://git.kernel.org/stable/c/db8d634128d2ba88d79c0b601e983ebe14bb0519