From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154480; b=0ZKS8NaNj2pKSG12DwN5G7KCijSzQqS7d/xgZvMjQhi7NwiCoksOkVHyn6OQ4UwqM4pJ Uqi97P52oUOdfsEeEJxz0fPbojyqIjWlWWZ3X1socm4mhy1S5v3K2Xm5sVy/Y+SViWDZb RTBqm03B99tDmLD7gW39EBjqn2+7KVGIQyxta9VcOS2roFNI9NlS99XXTVtDvr3H+HLWZ vAdQOGHpg4NPCgo6JwS+EDgGZ1wqsX/fOoulubl/WmMUz8P7tk4uVQQnLBahiIcLrOhzi LRH/OIZdf93of/TyrOUz8xSKeZHSjACvE2+ae2O7N4YyBAv+OHbwUMB/oVO0xvdxP7w== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154480; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=3hcYWX8cS26Y3Bjn3ThoYhX7FqdLPE81Bo/pSD4Zg1g=; b=EGCcNmEKvK5rfoKLfRB8LyVuJBSjh7va7wTAgRQJmyPhSgyPa1cUYL+w4lqWBVaLcUDX 4TIVhIH1Ly2r2LeaWknrA4sVrQqARDbRAaZlTthZW1zRRK2n9fI0ogE0k8mPOORVk5jXh U7t3/L0B5eIq19TGsXWZZTlWB5q8k+MxnTHMGSlzheUnQFPo0IMFhebzbJA7/HOhubF6+ COO1HdQSTtfH88VELcy+zRm3BbipkeaEycIg7e0YjCKiwdNC4NCXpf506Tnmqi8DE6A+h C0Rppx62MN84094qh9W6M6doXPn0Qfjzq60FEuGEZt6MgjuFVZAVDwcfqUnrm0hTdqQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=nqJA1XVI; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4D4BA606A502 for ; Fri, 20 Nov 2026 06:01:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=nqJA1XVI Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9C58E1F000C6; Fri, 20 Nov 2026 06:01:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154480; bh=3hcYWX8cS26Y3Bjn3ThoYhX7FqdLPE81Bo/pSD4Zg1g=; h=From:To:Cc:Subject:Date:Reply-To; b=nqJA1XVICzNJkc1PwmFseF/rFE72xoBe90oQ2cVB3VP2WiXuqpGWdyrahnBQTOrhF ARwbWWENvb96vHgSEilGKs8NYjpth89v3xjLNhXIMqoV+cVVXDd3+xoWNi/gBZHeTQ tqiMV3OvD3mbGVkfSjFcyQpBrIMjbAZKFy4ZXoV0= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99720: hwmon: chipcap2: fix IRQ teardown ordering Date: Fri, 20 Nov 2026 06:51:46 +0100 Message-ID: <2026112009-CVE-2026-99720-27a0@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2310; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=rqaezi6o17IxVMF55qlSQ3OHUbxQlFG34b7TWPbpzBo=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/70+qTvBi6KhVFdwzd/16Eb52/lqnAuu0Bje7ZY/qB e6ZsSd1xLIwCDIxyIopsnzZxnN0f8UhRS9D29Mwc1iZQIYwcHEKwESyhBgW3GBMCClfLXdrje+e N/NeeR31Xa9QwTA/5V0+b1PCsf5IZ55OD0/Rj4HM7roA 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: hwmon: chipcap2: fix IRQ teardown ordering The threaded IRQs are currently requested before the hwmon device is registered. Since devres releases resources in reverse order, the hwmon device is unregistered before the IRQs are freed during driver teardown. An IRQ may therefore still run after the hwmon device has been released and access the stale data->hwmon pointer. Separate IRQ discovery from IRQ registration so that the IRQ numbers and alarm visibility flags are initialized before registering the hwmon device while the IRQs are released before the hwmon device during devres cleanup. The Linux kernel CVE team has assigned CVE-2026-99720 to this issue. Affected and fixed versions =========================== Issue introduced in 6.9 with commit 3af350929e752fe72f0457033d448bff9aac695a and fixed in 7.3.5 with commit a205f2113200c6357e0526c94caaa4c2aceb2fc7 Issue introduced in 6.9 with commit 3af350929e752fe72f0457033d448bff9aac695a and fixed in 7.4-rc2 with commit d2a66c515d7730fd453485ffb306c412f1f46d72 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-99720 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/hwmon/chipcap2.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/a205f2113200c6357e0526c94caaa4c2aceb2fc7 https://git.kernel.org/stable/c/d2a66c515d7730fd453485ffb306c412f1f46d72