CVE-2026-80772
HID: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler()
Reported by linux · Published September 4, 2026
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.
EPSS 0.22% · 11.9th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | d4cabd4089adb59cf7974915737c52cc47a9bb1b, bd397c4123a4bc084913d8c7fdb40ef94e9f8172, addca61f9a23c0d20a387c2040e70479f54518e1, 51cfd1adbe7a46bb08af162abb3ab3b6820e2d15, 34725ed4719da424113db8449fb5485aaf71a913, 33ea29f8b6141f2d265de807e110a6435b355cb0, 27b376b945c0aac46fcdfcc950b14a85b874b557 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 2af16c1f846bd60240745bbd3afa13d5f040c61a, 2af16c1f846bd60240745bbd3afa13d5f040c61a, 2af16c1f846bd60240745bbd3afa13d5f040c61a |
| Linux | Linux | 5.16, 0, 6.1.185 |
| Linux | Linux | 7.3, 0, 6.1.185 |
| linux | linux_kernel | 5.16, 5.16, 5.16 |
Timeline
- Sep 4, 2026 Coalition ESS Score
- Sep 4, 2026 CVE Published
- Sep 5, 2026 EPSS Score (14 in total, the first dated here)
- Sep 15, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-80772
vulnetix vdb fixes CVE-2026-80772
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80772/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart