firmware_loader: Fix recursive lock in device_cache_fw_images()
Summary
| CVE | CVE-2026-74331 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-15 06:22:33 UTC |
| Updated | 2026-08-17 06:19:27 UTC |
| 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. |
Risk And Classification
EPSS: 0.001900000 probability, percentile 0.089730000 (date 2026-08-17)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected ac39b3ea73aacde876d1d5ee1ca3e2719f771482 806cb8fabfde7f830da5ae87777d52fdf50c4774 git | Not specified |
| CNA | Linux | Linux | affected ac39b3ea73aacde876d1d5ee1ca3e2719f771482 7865a1bfd20d10c03b083a5fc392d907ca5099b3 git | Not specified |
| CNA | Linux | Linux | affected ac39b3ea73aacde876d1d5ee1ca3e2719f771482 490b0385e4cfac691f7b18dde821c13e77b4770b git | Not specified |
| CNA | Linux | Linux | affected ac39b3ea73aacde876d1d5ee1ca3e2719f771482 38149b57427c736c08d9aa4c7b87deacd53e9e63 git | Not specified |
| CNA | Linux | Linux | affected ac39b3ea73aacde876d1d5ee1ca3e2719f771482 a5b2a68a391b05d54552f13548a72a46c65006f7 git | Not specified |
| CNA | Linux | Linux | affected ac39b3ea73aacde876d1d5ee1ca3e2719f771482 f25d6e4ec4c257030592bd671f113cf9584c52f0 git | Not specified |
| CNA | Linux | Linux | affected ac39b3ea73aacde876d1d5ee1ca3e2719f771482 c0f2dedd41fe14dbe076c1672214802fb42cd8c8 git | Not specified |
| CNA | Linux | Linux | affected ac39b3ea73aacde876d1d5ee1ca3e2719f771482 d3ec78f8f8d48a04a9fac38d47275c34645e5103 git | Not specified |
| CNA | Linux | Linux | affected 3.7 | Not specified |
| CNA | Linux | Linux | unaffected 3.7 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.261 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.212 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.178 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.145 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.97 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.40 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.5 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/c0f2dedd41fe14dbe076c1672214802fb42cd8c8 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/d3ec78f8f8d48a04a9fac38d47275c34645e5103 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/a5b2a68a391b05d54552f13548a72a46c65006f7 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f25d6e4ec4c257030592bd671f113cf9584c52f0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/7865a1bfd20d10c03b083a5fc392d907ca5099b3 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/38149b57427c736c08d9aa4c7b87deacd53e9e63 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/806cb8fabfde7f830da5ae87777d52fdf50c4774 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/490b0385e4cfac691f7b18dde821c13e77b4770b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.