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 988A138332F for ; Sat, 15 Aug 2026 06:35:26 +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=1786775727; cv=none; b=J95at9s248evLxywkCbiwDcupHAPuGSAeZwUo2gb382jkVrISJO7XS3PlVCqn5jIIMqIAeZZEKEZS9PHOtjTjQYWQ0JVWxtSxxmS0/g6XKxTD2uH64OIG9VeW3Mq5Y6tTaE2Zj6F8oX2Jhi7ME8lkxVoQOyuYceWNTY9r1mUYS4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786775727; c=relaxed/simple; bh=MSNHu8YvZqJxu5DDzTZFKKzFTxlra6SPSFK/qVV9AmQ=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=HBG2n99vdY0zR2jl3014NmYCw5ZGJcHh48nPLGfrvkCfhrjm7IrhFOAEpu45opTyNEemFvpOUCjfAqdfcvgKWjp1P/3JhsI16E410oEbD9iQhL6Jpt2j3DmQO50wm9XFrFhs6NGuf70wj5B24JoOcwHCwJgdN7UVKWqIcOUU36E= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=RO1Ehiba; 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="RO1Ehiba" Received: by smtp.kernel.org (Postfix) with ESMTPSA id ADD3F1F000E9; Sat, 15 Aug 2026 06:35:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1786775726; bh=g808JWMLKZKQk9GEZo0dlYM+F+bz2KtPr0+hytNyVJY=; h=From:To:Cc:Subject:Date:Reply-To; b=RO1EhibateoNt7uTV2Ego8PRFSVbTGdZyWgdnFZ8ZwM/CiIJuahWBZLCunAxuEgm7 J9ivJhTriZ0bJXVlf5m/bE2oB2QXIMAIl+6JwFwKxNcNiX6w4LMOzYyx0ogKMrAR1Y ol95Lob35mMukb1UrfRJgxrxvaBG/B/FTaBxpnU4= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-74331: firmware_loader: Fix recursive lock in device_cache_fw_images() Date: Sat, 15 Aug 2026 15:10:58 +0900 Message-ID: <2026081555-CVE-2026-74331-5c62@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=4427; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=+Mw6CAGyQmOtxpN9BpKjUh0C+nnU74cSFnMOgegE4E8=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkNjPwn7274svVXbLzm1e9P3j85UhwpFuA3MTJ1fdAMc c232Y8XdsSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEWgIYFiw1yevfKLNy2u4H K+7LfE5ImFtseYdhQe/q3GUsbvINdw4+4nhx/PBFlvjGpQA= 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: firmware_loader: Fix recursive lock in device_cache_fw_images() A recursive locking deadlock can occur in the firmware loader's power management notification handler. During system suspend or hibernation preparation, fw_pm_notify() calls device_cache_fw_images(). This function acquires fw_lock to set the firmware cache state to FW_LOADER_START_CACHE and then iterates over all devices using dpm_for_each_dev() while still holding the lock. For each device, dev_cache_fw_image() schedules asynchronous work to cache the firmware. If memory allocation for the async work entry fails (e.g., in out-of-memory conditions), async_schedule_node_domain() falls back to executing the work function synchronously in the current thread. The synchronous execution path (__async_dev_cache_fw_image() -> cache_firmware() -> request_firmware() -> assign_fw()) attempts to acquire fw_lock again. Since the current thread already holds fw_lock, this results in a recursive locking deadlock. Fix this by releasing fw_lock immediately after updating the cache state and before calling dpm_for_each_dev(). The lock is only needed to protect the state update. Concurrent firmware requests will correctly see the FW_LOADER_START_CACHE state and use the piggyback mechanism, which is independently protected by its own fwc->name_lock. The Linux kernel CVE team has assigned CVE-2026-74331 to this issue. Affected and fixed versions =========================== Issue introduced in 3.7 with commit ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and fixed in 5.10.261 with commit 806cb8fabfde7f830da5ae87777d52fdf50c4774 Issue introduced in 3.7 with commit ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and fixed in 5.15.212 with commit 7865a1bfd20d10c03b083a5fc392d907ca5099b3 Issue introduced in 3.7 with commit ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and fixed in 6.1.178 with commit 490b0385e4cfac691f7b18dde821c13e77b4770b Issue introduced in 3.7 with commit ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and fixed in 6.6.145 with commit 38149b57427c736c08d9aa4c7b87deacd53e9e63 Issue introduced in 3.7 with commit ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and fixed in 6.12.97 with commit a5b2a68a391b05d54552f13548a72a46c65006f7 Issue introduced in 3.7 with commit ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and fixed in 6.18.40 with commit f25d6e4ec4c257030592bd671f113cf9584c52f0 Issue introduced in 3.7 with commit ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and fixed in 7.1.5 with commit c0f2dedd41fe14dbe076c1672214802fb42cd8c8 Issue introduced in 3.7 with commit ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and fixed in 7.2-rc1 with commit d3ec78f8f8d48a04a9fac38d47275c34645e5103 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-74331 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/base/firmware_loader/main.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/806cb8fabfde7f830da5ae87777d52fdf50c4774 https://git.kernel.org/stable/c/7865a1bfd20d10c03b083a5fc392d907ca5099b3 https://git.kernel.org/stable/c/490b0385e4cfac691f7b18dde821c13e77b4770b https://git.kernel.org/stable/c/38149b57427c736c08d9aa4c7b87deacd53e9e63 https://git.kernel.org/stable/c/a5b2a68a391b05d54552f13548a72a46c65006f7 https://git.kernel.org/stable/c/f25d6e4ec4c257030592bd671f113cf9584c52f0 https://git.kernel.org/stable/c/c0f2dedd41fe14dbe076c1672214802fb42cd8c8 https://git.kernel.org/stable/c/d3ec78f8f8d48a04a9fac38d47275c34645e5103