Skip to main content
VulnerabilityPublished Updated

CVE-2026-74331: Linux kernel · firmware_loader: Fix recursive lock in device_cache_fw_images()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f25d6e4ec4c257030592bd671f113cf9584c52f0 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 18:03 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in f25d6e4ec4c257030592bd671f113cf9584c52f0, d3ec78f8f8d48a04a9fac38d47275c34645e5103, c0f2dedd41fe14dbe076c1672214802fb42cd8c8 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ac39b3ea73aacde876d1d5ee1ca3e2719f771482, < f25d6e4ec4c257030592bd671f113cf9584c52f0
Fixed in
  • f25d6e4ec4c257030592bd671f113cf9584c52f0
LinuxLinuxAffected
  • ≥ ac39b3ea73aacde876d1d5ee1ca3e2719f771482, < d3ec78f8f8d48a04a9fac38d47275c34645e5103
Fixed in
  • d3ec78f8f8d48a04a9fac38d47275c34645e5103
LinuxLinuxAffected
  • ≥ ac39b3ea73aacde876d1d5ee1ca3e2719f771482, < c0f2dedd41fe14dbe076c1672214802fb42cd8c8
Fixed in
  • c0f2dedd41fe14dbe076c1672214802fb42cd8c8
LinuxLinuxAffected
  • ≥ ac39b3ea73aacde876d1d5ee1ca3e2719f771482, < a5b2a68a391b05d54552f13548a72a46c65006f7
Fixed in
  • a5b2a68a391b05d54552f13548a72a46c65006f7
LinuxLinuxAffected
  • ≥ ac39b3ea73aacde876d1d5ee1ca3e2719f771482, < 38149b57427c736c08d9aa4c7b87deacd53e9e63
Fixed in
  • 38149b57427c736c08d9aa4c7b87deacd53e9e63
LinuxLinuxAffected
  • ≥ ac39b3ea73aacde876d1d5ee1ca3e2719f771482, < 7865a1bfd20d10c03b083a5fc392d907ca5099b3
Fixed in
  • 7865a1bfd20d10c03b083a5fc392d907ca5099b3

AI-suggested

A fix is available in the Linux kernel as indicated by the listed fixed commit versions. Users and administrators should update to a kernel version that includes the fix identified by the provided commit hashes. No additional mitigation is required as the patch resolves the deadlock by adjusting lock handling in the firmware loader.

Description

A deadlock vulnerability was fixed in the Linux kernel's firmware loader component. The issue occurs due to recursive locking of fw_lock during system suspend or hibernation preparation when caching firmware images. This deadlock arises if asynchronous work scheduling fails and the work executes synchronously, causing the lock to be acquired twice by the same thread. The fix involves releasing the lock before iterating over devices to prevent recursive locking.

References

Community reviews

Loading reviews…