Heimdall Security Logo

CVE-2026-74331

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <f25d6e4ec4c257030592bd671f113cf9584c52f0, <=6.1.*, 6.18.40, <=6.12.*, 7.1.5, <c0f2dedd41fe14dbe076c1672214802fb42cd8c8, 0, <=7.1.*, 6.1.178, <=5.10.*, <=6.6.*, 6.12.97, ac39b3ea73aacde876d1d5ee1ca3e2719f771482, <7865a1bfd20d10c03b083a5fc392d907ca5099b3, <=6.18.*, 5.15.212, <490b0385e4cfac691f7b18dde821c13e77b4770b, 6.6.145, 5.10.261, <a5b2a68a391b05d54552f13548a72a46c65006f7, <3.7, <806cb8fabfde7f830da5ae87777d52fdf50c4774, <d3ec78f8f8d48a04a9fac38d47275c34645e5103, <=*, 3.7, <=5.15.*, 7.2, <38149b57427c736c08d9aa4c7b87deacd53e9e63

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.

Gravité et risque d'exploitation

CVE-2026-74331 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.24 %, ce qui la place devant 13.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <f25d6e4ec4c257030592bd671f113cf9584c52f0, <=6.1.*, 6.18.40, <=6.12.*, 7.1.5, <c0f2dedd41fe14dbe076c1672214802fb42cd8c8, 0, <=7.1.*, 6.1.178, <=5.10.*, <=6.6.*, 6.12.97, ac39b3ea73aacde876d1d5ee1ca3e2719f771482, <7865a1bfd20d10c03b083a5fc392d907ca5099b3, <=6.18.*, 5.15.212, <490b0385e4cfac691f7b18dde821c13e77b4770b, 6.6.145, 5.10.261, <a5b2a68a391b05d54552f13548a72a46c65006f7, <3.7, <806cb8fabfde7f830da5ae87777d52fdf50c4774, <d3ec78f8f8d48a04a9fac38d47275c34645e5103, <=*, 3.7, <=5.15.*, 7.2, <38149b57427c736c08d9aa4c7b87deacd53e9e63) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE