HID: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler()
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.185, 6.12.106, 6.18.47, 6.6.154, 7.1.11, 7.2.1
- CVEs
- CVE-2026-80772
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 04:00 UTC · Revision 1
Source evidence
HID: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler()
core-osv · Original sourcePublished 4 Sept 2026, 15:12 UTC
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.
osv:CVE-2026-80772
Kernel
Fixed versions: 6.1.185, 6.6.154, 6.12.106, 6.18.47, 7.1.11, 7.2.1
Complete source record
{
"id": "5e2b0ae01ab594c5067653a537d4bef1e0582726dfd0b3a5d47cbbb12ee50581",
"url": "https://osv.dev/vulnerability/CVE-2026-80772",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "HID: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler()",
"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.",
"evidence": "osv:CVE-2026-80772",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.185",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.154",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.106",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.47",
"evidence": "/affected/1/ranges"
},
{
"value": "7.1.11",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.1",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-80772",
"aliases": [
"CVE-2026-80772"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "2af16c1f846bd60240745bbd3afa13d5f040c61a"
},
{
"fixed": "33ea29f8b6141f2d265de807e110a6435b355cb0"
},
{
"fixed": "bd397c4123a4bc084913d8c7fdb40ef94e9f8172"
},
{
"fixed": "addca61f9a23c0d20a387c2040e70479f54518e1"
},
{
"fixed": "51cfd1adbe7a46bb08af162abb3ab3b6820e2d15"
},
{
"fixed": "d4cabd4089adb59cf7974915737c52cc47a9bb1b"
},
{
"fixed": "34725ed4719da424113db8449fb5485aaf71a913"
},
{
"fixed": "27b376b945c0aac46fcdfcc950b14a85b874b557"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-80772.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.185"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.154"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.106"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.47"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.1.11"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "7.2.0"
},
{
"fixed": "7.2.1"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-80772.json"
}
}
],
"modified": "2026-10-28T02:30:42.094511887Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/27b376b945c0aac46fcdfcc950b14a85b874b557",
"https://git.kernel.org/stable/c/33ea29f8b6141f2d265de807e110a6435b355cb0",
"https://git.kernel.org/stable/c/34725ed4719da424113db8449fb5485aaf71a913",
"https://git.kernel.org/stable/c/51cfd1adbe7a46bb08af162abb3ab3b6820e2d15",
"https://git.kernel.org/stable/c/addca61f9a23c0d20a387c2040e70479f54518e1",
"https://git.kernel.org/stable/c/bd397c4123a4bc084913d8c7fdb40ef94e9f8172",
"https://git.kernel.org/stable/c/d4cabd4089adb59cf7974915737c52cc47a9bb1b",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/80xxx/CVE-2026-80772.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-80772",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/80xxx/CVE-2026-80772.json"
}
},
"related_cves": [
{
"value": "CVE-2026-80772",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 510057,
"published_at": "2026-09-04T15:12:44.445+00:00"
}