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 83B7358122B for ; Fri, 11 Sep 2026 19:51:37 +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=1789156310; cv=none; b=A0p96QRdksZIJ4fZINqpmmoyUdnYm0Uba+NEwCLJ8msDaYb5yhNcfS5ubPbaqTqnpj8v96vCfxPm6OMG3ak+hkpVLKiB7kcwyV44ugUzyW6YaVu7aVNTQRMvWmU1SJ2lc/BAvPinBkdjBzDiz9e9QT5J14y+8sXYUJzGSMsnGVM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156310; c=relaxed/simple; bh=i7e0GSTBfSmM8ED5D5opGiqCFCprdvwxNJ/sDd24OiQ=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=r90cyVYYxOvFOv11DVUxmfWlYpl/+UeCzz74WN/MjIPU8YpHM+6ZtnhXbZ088ybICQ6jEL2j5cUSdRHn+gaSpZ250u6xbHwhN/n3MMYqo1n+YzrNQgjuW7p24I2RWZk9HIK0s2Iv+jMOYyNRcgkuCN6F8NYkRJnepO0EFD8vAf4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=0g+fzRCP; 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="0g+fzRCP" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1DF6D1F00893; Fri, 11 Sep 2026 19:51:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789156295; bh=Rdwn7MFXoMyd28SjFdR1v86ErY7dSDboNp1E+lmzIAE=; h=From:To:Cc:Subject:Date:Reply-To; b=0g+fzRCPTJnoEz96LsB4SlZgJiXBKFwhIDEwWJ2+SyHgDcrJ4CIO/mCcie7OC7lwG SeJYbnww0lqIVFJ4C/gY3gRV/mb6D9ngyyqeVQRhfKEy2QXG+J03KzmvXIBcWXKICt 2btwGAeWWrW7e8zABtFaYgaop49I1xQGamQG2d5M= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89442: platform/x86: ISST: Validate socket ID in clos_assoc ioctl Date: Fri, 11 Sep 2026 21:42:11 +0200 Message-ID: <2026091156-CVE-2026-89442-6596@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=3049; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=L8EDSYtoNvSqfnu4Fs8D/D70KOoEgXmo7kt/WGHkiM0=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLIj36Tn1TPKMkZSzfoGvw9+Pnna6Zq7aXansvnLv5m VpgwcLWjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZjIr58M8/O2pGqH9628zqxS tPpKaGjmeyMlN4YFc6/rHpl27Fgwd6n6O6+0XwpLBKIPAwA= 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: platform/x86: ISST: Validate socket ID in clos_assoc ioctl isst_if_clos_assoc() validates the user-supplied socket_id with 'socket_id > topology_max_packages()', but isst_common.sst_inst[] is allocated with topology_max_packages() entries, so the valid index range is [0, topology_max_packages()). The '>' comparison lets socket_id == topology_max_packages() pass and index one entry past the array. In addition, isst_common.sst_inst[socket_id] is NULL for an in-range package that has no bound TPMI SST instance, and the pointer is used without a NULL check. Both the out-of-bounds entry and the NULL pointer are then dereferenced by map_partition_power_domain_id() and the following power_domain_info access. Reject socket_id >= topology_max_packages() and a NULL sst_inst, matching the checks already performed by get_instance(). The Linux kernel CVE team has assigned CVE-2026-89442 to this issue. Affected and fixed versions =========================== Issue introduced in 6.4 with commit 12a7d2cb811dd8a884dea088a2701fcb8d00136e and fixed in 6.12.109 with commit 0d90ab5f80e19cddfeb0c9fab47a1f34aa932075 Issue introduced in 6.4 with commit 12a7d2cb811dd8a884dea088a2701fcb8d00136e and fixed in 6.18.50 with commit 82e707eff9e3b7ef6d96ecc23ea8876d20c7d6ca Issue introduced in 6.4 with commit 12a7d2cb811dd8a884dea088a2701fcb8d00136e and fixed in 7.2.4 with commit 207b4dc6eb100141b122b2602504a1429a4b6558 Issue introduced in 6.4 with commit 12a7d2cb811dd8a884dea088a2701fcb8d00136e and fixed in 7.3-rc1 with commit a89f07db0cb95c54dac4a8406c79a04e44a73c3c 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-89442 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/platform/x86/intel/speed_select_if/isst_tpmi_core.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/0d90ab5f80e19cddfeb0c9fab47a1f34aa932075 https://git.kernel.org/stable/c/82e707eff9e3b7ef6d96ecc23ea8876d20c7d6ca https://git.kernel.org/stable/c/207b4dc6eb100141b122b2602504a1429a4b6558 https://git.kernel.org/stable/c/a89f07db0cb95c54dac4a8406c79a04e44a73c3c