From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AF4744F0526 for ; Fri, 4 Sep 2026 15:14:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788534850; cv=none; b=ixOl7fVSq/bwzupVm9TUJhekKWPwy58sT0d3vlMpNH/AO+9JRMGYBcuHcVOSpPOm/3/HLAl1Aw8/ndCollrIb2L6yhFZEJaGVUUgSHHsDpAbC8YXYD+CkG9Gcy6IROnNnmSJNBqH3xeC1ucMEMjjx0t0n0LztD30GsLBv0gSISY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788534850; c=relaxed/simple; bh=Df4stuRPk5+l14oIRGBN0imD3RlCxPpQjTkddha/B70=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=soasTE5WvNi1MhFr9czcOgYzwXaXo5vXIeb2WR7wUUhIb9H1+rp2arAxVprz1WOEIgG6Xjd9brxShG7eIsmjoRiUn81MR1eUKg5lfLv+/qAaKJCWBQfr0pOjsdbT4khCnfMhwMmKp7rUELblP+js+sxIMB5+j2N69ZemQanWyE4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=2DcQQcSp; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="2DcQQcSp" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A5D711F00A3D; Fri, 4 Sep 2026 15:14:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1788534849; bh=PyF3H2qGPKq+38egotO7WgX2hd6+KlSCjY3hPexZM2c=; h=From:To:Cc:Subject:Date:Reply-To; b=2DcQQcSpuI2HMc81iAFOy9Yj/7KQTK56trXErL5ICULDwmXQdwh5iHjl5X3ft56GS uf2FCL9msmn1vhAoVC0WtHwBFPsbvbC3PDvVod2eWOq6qNVNaoFXc8mX4ZgNPNq0H6 fvaNP37H2vBordkYLDagfLSSY4jfwW8vA/J1lqWw= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80772: HID: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler() Date: Fri, 4 Sep 2026 17:11:11 +0200 Message-ID: <2026090402-CVE-2026-80772-6497@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4266; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=xzE2QX4EMFEnPj+QfKO4T9LALqL1+Kkhl9ylqTc5+V0=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmz7rc1NP3hPbS4X8Yn4Z5Tz7GHFVs60mLffdx6Lk1T/ WdzY1htRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEyERYlhnsZk/lCxNr80Huvg 0slFlrlFp4IUGRacrni57XJ7ZYiBw/3Loddf3fSy8ZsGAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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. The Linux kernel CVE team has assigned CVE-2026-80772 to this issue. Affected and fixed versions =========================== Issue introduced in 5.16 with commit 2af16c1f846bd60240745bbd3afa13d5f040c61a and fixed in 6.1.185 with commit 33ea29f8b6141f2d265de807e110a6435b355cb0 Issue introduced in 5.16 with commit 2af16c1f846bd60240745bbd3afa13d5f040c61a and fixed in 6.6.154 with commit bd397c4123a4bc084913d8c7fdb40ef94e9f8172 Issue introduced in 5.16 with commit 2af16c1f846bd60240745bbd3afa13d5f040c61a and fixed in 6.12.106 with commit addca61f9a23c0d20a387c2040e70479f54518e1 Issue introduced in 5.16 with commit 2af16c1f846bd60240745bbd3afa13d5f040c61a and fixed in 6.18.47 with commit 51cfd1adbe7a46bb08af162abb3ab3b6820e2d15 Issue introduced in 5.16 with commit 2af16c1f846bd60240745bbd3afa13d5f040c61a and fixed in 7.1.11 with commit d4cabd4089adb59cf7974915737c52cc47a9bb1b Issue introduced in 5.16 with commit 2af16c1f846bd60240745bbd3afa13d5f040c61a and fixed in 7.2.1 with commit 34725ed4719da424113db8449fb5485aaf71a913 Issue introduced in 5.16 with commit 2af16c1f846bd60240745bbd3afa13d5f040c61a and fixed in 7.3-rc1 with commit 27b376b945c0aac46fcdfcc950b14a85b874b557 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-80772 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/hid/hid-nintendo.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/33ea29f8b6141f2d265de807e110a6435b355cb0 https://git.kernel.org/stable/c/bd397c4123a4bc084913d8c7fdb40ef94e9f8172 https://git.kernel.org/stable/c/addca61f9a23c0d20a387c2040e70479f54518e1 https://git.kernel.org/stable/c/51cfd1adbe7a46bb08af162abb3ab3b6820e2d15 https://git.kernel.org/stable/c/d4cabd4089adb59cf7974915737c52cc47a9bb1b https://git.kernel.org/stable/c/34725ed4719da424113db8449fb5485aaf71a913 https://git.kernel.org/stable/c/27b376b945c0aac46fcdfcc950b14a85b874b557