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 2A57F503BC1 for ; Wed, 16 Sep 2026 10:40:24 +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=1789555227; cv=none; b=MnoUuYd8ovKMeabKGVizpnRL8STisFzBp8we/UYJfrsb4liXjAcOvOZ+A3p5sRc40L67ul6BEYFTH0HwMYliOLnbFUlAp9Woxm3kmjIQ66NHQVTAeKVjl8md39ExHXwTOKqOh4c5JKo9lLd3NsUzIRmASfQCIHEjpVGP/D0pdy0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789555227; c=relaxed/simple; bh=WUVZD8kUWKPEUWAx3TZDHWToVqT12LInvmqBC/o+i/8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=ZeaqjNpepPh8gi4BZRYqnjjiPcFyvgyytLnIa0qhF0jHyODemlF09HjzJ+igpVZ+8UQ2Q7+IoEu7zzbOKNkI3dMvB7H4V2xfLqB9KMNVdG6nIaWlGqyqUqbaMLuynRkafdDaPtL60O+FqUHRMbsL2gma0ny7D4fczT9WECqNQHA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=OVE6U82C; 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="OVE6U82C" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0541D1F0089B; Wed, 16 Sep 2026 10:40:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789555223; bh=k2LRKffc0KcmCNNDuSBPfvpJKQcmVmY9HzOCFmESVAw=; h=From:To:Cc:Subject:Date:Reply-To; b=OVE6U82C7hS8nhyla+TIqZJ8eZALCu0VVzuUy7eSFrUBbkc5zBARxrMiczgEMLv19 eGIW7Z2US1nDQPYeVY7DQb1eqAwqXwefUUS8BuKiLVIRPS3Md37vkwe9ccOeEDJ2Hz vSnT4EZYlQIYWJjlRgtyJbowBOI+WdGBGS1L3wVo= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89946: ASoC: cs35l33: drain threaded IRQ before runtime suspend Date: Wed, 16 Sep 2026 11:31:16 +0100 Message-ID: <2026091648-CVE-2026-89946-e108@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=4203; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=TXMZMZV24ciDFKvIUDeQLyk7XrNTXXtZ/ch4Hw32FK4=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmr8ucoTFo+fclWPo6m0hrO7dMPJR7l/u2wPO/lWtZH3 FaF9e0MHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRUFaGuRKX3Hn2O/a/CmX6 E3aZ45ME4wH2ZwzzIyqZeN1t34sbTy6WdS862RycXRYHAA== 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: ASoC: cs35l33: drain threaded IRQ before runtime suspend cs35l33_runtime_suspend() currently switches the codec into regcache_cache_only(true) and powers it down without first quiescing the threaded IRQ registered by devm_request_threaded_irq(). That leaves a window where cs35l33_irq_thread() can still run after suspend has closed off live register access. A running system can reach this during runtime PM while the driver still has critical fault IRQs unmasked. If the threaded handler runs in that window, it reads volatile INT_STATUS_1/2 after cache_only has been enabled, ignores the regmap_read() failures, and can still drive the AMP_SHORT_RLS, CAL_ERR_RLS, OTE_RLS, and OTW_RLS release paths. Use disable_irq() before entering cache_only/power-off so any in-flight threaded handler is drained and no new IRQ thread can run during the suspended state. Re-enable the IRQ only after runtime_resume() has restored live register access with regcache_sync(). Since probe only warns if devm_request_threaded_irq() fails, track whether the IRQ was actually installed before disabling or re-enabling it. The Linux kernel CVE team has assigned CVE-2026-89946 to this issue. Affected and fixed versions =========================== Issue introduced in 4.8 with commit 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and fixed in 5.10.270 with commit d07799302721d381aef834fac8a11d196894eccb Issue introduced in 4.8 with commit 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and fixed in 5.15.221 with commit 5b5311427e54d9c0d07178ee42df68ba44c2d5ca Issue introduced in 4.8 with commit 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and fixed in 6.1.188 with commit a04722542c76ce861031384480825afded8cc4f4 Issue introduced in 4.8 with commit 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and fixed in 6.6.157 with commit 614c2616ea677abfbed917a92bdc5141efff3536 Issue introduced in 4.8 with commit 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and fixed in 6.12.110 with commit 6ae98918240585eb2ad32b097c4810f4e2dabe88 Issue introduced in 4.8 with commit 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and fixed in 6.18.51 with commit 6e369bc46663b4bfce3d5f8b8ed08e71ecea13a2 Issue introduced in 4.8 with commit 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and fixed in 7.2.5 with commit 84cf6acd01a1ec8f30276578a039216327af782e Issue introduced in 4.8 with commit 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 and fixed in 7.3-rc1 with commit e074c12c428c633e079154301207a6079a208583 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-89946 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: sound/soc/codecs/cs35l33.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/d07799302721d381aef834fac8a11d196894eccb https://git.kernel.org/stable/c/5b5311427e54d9c0d07178ee42df68ba44c2d5ca https://git.kernel.org/stable/c/a04722542c76ce861031384480825afded8cc4f4 https://git.kernel.org/stable/c/614c2616ea677abfbed917a92bdc5141efff3536 https://git.kernel.org/stable/c/6ae98918240585eb2ad32b097c4810f4e2dabe88 https://git.kernel.org/stable/c/6e369bc46663b4bfce3d5f8b8ed08e71ecea13a2 https://git.kernel.org/stable/c/84cf6acd01a1ec8f30276578a039216327af782e https://git.kernel.org/stable/c/e074c12c428c633e079154301207a6079a208583