Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Fixed version: Linux Linux 38149b57427c736c08d9aa4c7b87deacd53e9e63, 490b0385e4cfac691f7b18dde821c13e77b4770b, 7865a1bfd20d10c03b083a5fc392d907ca5099b3.

Low priority for now. Upgrade to Linux Linux 38149b57427c736c08d9aa4c7b87deacd53e9e63, 490b0385e4cfac691f7b18dde821c13e77b4770b, 7865a1bfd20d10c03b083a5fc392d907ca5099b3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Aug 15, 2026
Updated
Nov 6, 2026
EPSS
0.2% · 14th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-74331

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.7affected
    • ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and later · before 806cb8fabfde7f830da5ae87777d52fdf50c4774affected · git
    • ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and later · before 7865a1bfd20d10c03b083a5fc392d907ca5099b3affected · git
    • ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and later · before 490b0385e4cfac691f7b18dde821c13e77b4770baffected · git
    • ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and later · before 38149b57427c736c08d9aa4c7b87deacd53e9e63affected · git
    • ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and later · before a5b2a68a391b05d54552f13548a72a46c65006f7affected · git
    • ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and later · before f25d6e4ec4c257030592bd671f113cf9584c52f0affected · git
    • ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and later · before c0f2dedd41fe14dbe076c1672214802fb42cd8c8affected · git
    • ac39b3ea73aacde876d1d5ee1ca3e2719f771482 and later · before d3ec78f8f8d48a04a9fac38d47275c34645e5103affected · git
    • before 3.7not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-74329Aug 15, 2026 · watchdog: unregister PM notifier on watchdog unregister
    0Monitor
  • ← EarlierCVE-2026-74330Aug 15, 2026 · configfs: fix lockless traversals of ->s_children
    31Monitor
  • Later →CVE-2026-74332Aug 15, 2026 · ASoC: amd: acp-sdw-sof: Bound DAI link iteration
    33Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux38149b57427c736c08d9aa4c7b87deacd53e9e63Vendor (CNA)
Linux Linux490b0385e4cfac691f7b18dde821c13e77b4770bVendor (CNA)
Linux Linux7865a1bfd20d10c03b083a5fc392d907ca5099b3Vendor (CNA)
Linux Linux806cb8fabfde7f830da5ae87777d52fdf50c4774Vendor (CNA)
Linux Linuxa5b2a68a391b05d54552f13548a72a46c65006f7Vendor (CNA)
Linux Linuxc0f2dedd41fe14dbe076c1672214802fb42cd8c8Vendor (CNA)
Linux Linuxd3ec78f8f8d48a04a9fac38d47275c34645e5103Vendor (CNA)
Linux Linuxf25d6e4ec4c257030592bd671f113cf9584c52f0Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records