CVE-2026-80772

HID: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler()

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: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler() joycon_ctlr_read_handler() casts an incoming HID input report to struct joycon_input_report and parses it, guarding the cast only with a 12-byte length check: if (size >= 12) /* make sure it contains the input report */ joycon_parse_report(ctlr, (struct joycon_input_report *)data); struct joycon_input_report is 49 bytes: a 13-byte header followed by a union whose IMU arm is 36 bytes. For an IMU report joycon_parse_report() -> joycon_parse_imu_report() walks that union (struct offsets 13..48), so a report of exactly 12 bytes with data[0] == JC_INPUT_IMU_DATA passes the guard yet is read up to 37 bytes past its declared length. The over-read bytes are decoded into accelerometer/gyroscope values and forwarded to userspace through the "(IMU)" input device, leaking driver-internal memory. data[0] and size are fully controlled by a malicious or spoofed Joy-Con/Pro Controller. Receive buffers are sized to the maximum report length, so this is an over-read within the allocation rather than a slab OOB, but the decoded bytes still reach userspace. The sibling subcmd path in joycon_ctlr_handle_event() already bounds the same cast correctly: if (size < sizeof(struct joycon_input_report) || data[0] != JC_INPUT_SUBCMD_REPLY) break; Use the same sizeof(struct joycon_input_report) bound here.

Affected

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

2af16c1f846bd60240745bbd3afa13d5f040c61a5.16
Vendor states this is fixed in 27b376b945c0aac46fcdfcc950b14a85b874b557 (fixed)
Vendor states this is fixed in 33ea29f8b6141f2d265de807e110a6435b355cb0 (fixed)
Vendor states this is fixed in 34725ed4719da424113db8449fb5485aaf71a913 (fixed)
Vendor states this is fixed in 51cfd1adbe7a46bb08af162abb3ab3b6820e2d15 (fixed)
Vendor states this is fixed in addca61f9a23c0d20a387c2040e70479f54518e1 (fixed)
Vendor states this is fixed in bd397c4123a4bc084913d8c7fdb40ef94e9f8172 (fixed)
Vendor states this is fixed in d4cabd4089adb59cf7974915737c52cc47a9bb1b (fixed)
Vendor states this is fixed in 5.16 (unaffected)
Vendor states this is fixed in 6.1.185 (unaffected)
Vendor states this is fixed in 6.12.106 (unaffected)
Vendor states this is fixed in 6.18.47 (unaffected)
Vendor states this is fixed in 6.6.154 (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