HID: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.185, 6.6.154, 6.12.106, 6.18.47, 7.1.11, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 2af16c1f846bd60240745bbd3afa13d5f040c61a · fixed in 33ea29f8b6141f2d265de807e110a6435b355cb0; From 2af16c1f846bd60240745bbd3afa13d5f040c61a · fixed in bd397c4123a4bc084913d8c7fdb40ef94e9f8172; From 2af16c1f846bd60240745bbd3afa13d5f040c61a · fixed in addca61f9a23c0d20a387c2040e70479f54518e1; From 2af16c1f846bd60240745bbd3afa13d5f040c61a · fixed in 51cfd1adbe7a46bb08af162abb3ab3b6820e2d15; From 2af16c1f846bd60240745bbd3afa13d5f040c61a · fixed in d4cabd4089adb59cf7974915737c52cc47a9bb1b; From 2af16c1f846bd60240745bbd3afa13d5f040c61a · fixed in 34725ed4719da424113db8449fb5485aaf71a913; From 2af16c1f846bd60240745bbd3afa13d5f040c61a · fixed in 27b376b945c0aac46fcdfcc950b14a85b874b557
- Linux Linux
5.16
- KernelLinux
From 5.16.0 · fixed in 6.1.185; From 6.2.0 · fixed in 6.6.154; From 6.7.0 · fixed in 6.12.106; From 6.13.0 · fixed in 6.18.47; From 6.19.0 · fixed in 7.1.11; From 7.2.0 · fixed in 7.2.1
References 7
git.kernel.org
- stable/c/33ea29f8b6141f2d265de807e110a6435b355cb0
- stable/c/bd397c4123a4bc084913d8c7fdb40ef94e9f8172
- stable/c/addca61f9a23c0d20a387c2040e70479f54518e1
- stable/c/51cfd1adbe7a46bb08af162abb3ab3b6820e2d15
- stable/c/d4cabd4089adb59cf7974915737c52cc47a9bb1b
- stable/c/34725ed4719da424113db8449fb5485aaf71a913
- stable/c/27b376b945c0aac46fcdfcc950b14a85b874b557