System hang via recursive firmware-cache lock
Published Aug 15, 2026 · Updated Aug 15, 2026
Deadlock in the Linux kernel firmware loader allows local users to hang the system during suspend or hibernation under memory pressure. device_cache_fw_images() holds fw_lock while synchronous fallback caching reaches assign_fw(), which tries to acquire the same lock again. Triggering requires power-state preparation plus asynchronous-work allocation failure, leaving the power-management path hung.
Summary
What happened
Deadlock in the Linux kernel firmware loader allows local users to hang the system during suspend or hibernation under memory pressure. device_cache_fw_images() holds fw_lock while synchronous fallback caching reaches assign_fw(), which tries to acquire the same lock again. Triggering requires power-state preparation plus asynchronous-work allocation failure, leaving the power-management path hung.
The record
- CVE
- CVE-2026-74331
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-833, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.7
- Affected versionversion=ac39b3ea73aacde876d1d5ee1ca3e2719f771482 <38149b57427c736c08d9aa4c7b87deacd53e9e63
- Affected versionversion=ac39b3ea73aacde876d1d5ee1ca3e2719f771482 <490b0385e4cfac691f7b18dde821c13e77b4770b
- Affected versionversion=ac39b3ea73aacde876d1d5ee1ca3e2719f771482 <7865a1bfd20d10c03b083a5fc392d907ca5099b3
- Affected versionversion=ac39b3ea73aacde876d1d5ee1ca3e2719f771482 <806cb8fabfde7f830da5ae87777d52fdf50c4774
- Affected versionversion=ac39b3ea73aacde876d1d5ee1ca3e2719f771482 <a5b2a68a391b05d54552f13548a72a46c65006f7
- Affected versionversion=ac39b3ea73aacde876d1d5ee1ca3e2719f771482 <c0f2dedd41fe14dbe076c1672214802fb42cd8c8
- Affected versionversion=ac39b3ea73aacde876d1d5ee1ca3e2719f771482 <d3ec78f8f8d48a04a9fac38d47275c34645e5103
- Affected versionversion=ac39b3ea73aacde876d1d5ee1ca3e2719f771482 <f25d6e4ec4c257030592bd671f113cf9584c52f0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- syzbot possible deadlock in assign_fw reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo