Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-74331

kernel: firmware_loader: Fix recursive lock in device_cache_fw_images()

Overview

Published
15 Aug 2026
Modified
6 Nov 2026
Low CVE
0 Registry packages
344 OS packages
10 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

5.5 · LOW

CVSS 3.1 base score, scored by redhat.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 102 fixes

Oracle Linux 2 releases · 2 packages

fixed 3
bpftool kernel-uek
Oracle Linux fixes for CVE-2026-74331
ReleasePackageFixed in
8 bpftool +13 5.15.0-324.217.5.2.el8uek
9 bpftool +2 5.15.0-324.217.5.2.el9uek
9 kernel-uek +34 6.12.0-206.104.3.3.el9uek

Photon OS 1 release · 1 package

fixed 1
bpftool
Photon OS fixes for CVE-2026-74331
ReleasePackageFixed in
5.0 bpftool +10 6.12.103-1.ph5

Red Hat 2 releases · 1 package

affected 2
bpftool
Red Hat fixes for CVE-2026-74331
ReleasePackageFixed in
8 bpftool +45 affected
9 bpftool +106 affected

SUSE Linux Enterprise 3 releases · 5 packages

fixed 7
kernel-livepatch-6-4-0-150700-53-90-default cluster-md-kmp-default kernel-default-base kernel-64kb kernel-devel-nvidia
SUSE Linux Enterprise fixes for CVE-2026-74331
ReleasePackageFixed inAdvisory
15.7 kernel-livepatch-6-4-0-150700-53-90-default 1-150700.15.3.1 SUSE-SU-2026:5091-1
15.7 cluster-md-kmp-default +20 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1
15.7 kernel-default-base 6.4.0-150700.53.90.1.150700.17.51.1 SUSE-SU-2026:5091-1
16.0 cluster-md-kmp-default +2 6.12.0-160000.41.1 SUSE-SU-2026:24651-1
16.0 kernel-64kb +23 6.12.0-160000.41.1 SUSE-SU-2026:24662-1
16.0 kernel-default-base 6.12.0-160000.41.1.160000.2.32 SUSE-SU-2026:24662-1

1 more row

SUSE Linux Enterprise Micro 3 releases · 3 packages

fixed 6
kernel-default kernel-default-base kernel-64kb
SUSE Linux Enterprise Micro fixes for CVE-2026-74331
ReleasePackageFixed inAdvisory
6.0 kernel-default +5 6.4.0-159998.55.1 SUSE-SU-2026:24550-1
6.0 kernel-default-base 6.4.0-159998.55.1.159998.21.42 SUSE-SU-2026:24550-1
6.1 kernel-default +6 6.4.0-159998.55.1 SUSE-SU-2026:24619-1
6.1 kernel-default-base 6.4.0-159998.55.1.159998.21.41 SUSE-SU-2026:24619-1
6.2 kernel-64kb +11 6.12.0-160000.41.1 SUSE-SU-2026:24643-1
6.2 kernel-default-base 6.12.0-160000.41.1.160000.2.32 SUSE-SU-2026:24643-1

amazon linux 1 release · 4 packages

fixed 4
kernel-livepatch-6-1-180-225-360 bpftool bpftool6-12 bpftool6-18
amazon linux fixes for CVE-2026-74331
ReleasePackageFixed in
2023 kernel-livepatch-6-1-180-225-360 +2 1:1.0-0.amzn2023
2023 bpftool +16 1:6.1.180-225.360.amzn2023
2023 bpftool6-12 +16 1:6.12.100-125.179.amzn2023
2023 bpftool6-18 +17 1:6.18.41-94.142.amzn2023

debian 4 releases · 1 package

fixed 4
linux
debian fixes for CVE-2026-74331
ReleasePackageFixed in
11 linux 5.10.262-1
12 linux 6.1.180-1
13 linux 6.12.100-1
14 linux 7.1.5-1

echo 1 release · 1 package

fixed 1
linux
echo fixes for CVE-2026-74331
ReleasePackageFixed in
linux 6.12.100-1

openSUSE Leap 2 releases · 3 packages

fixed 5
cluster-md-kmp-64kb kernel-default-base cluster-md-kmp-nvidia64kb
openSUSE Leap fixes for CVE-2026-74331
ReleasePackageFixed inAdvisory
16.0 cluster-md-kmp-64kb +74 6.12.0-160000.41.1 openSUSE-SU-2026:22266-1
16.0 kernel-default-base 6.12.0-160000.41.1.160000.2.31 openSUSE-SU-2026:22266-1
16.1 cluster-md-kmp-nvidia64kb +11 6.12.0-160100.7.1 openSUSE-SU-2026:22307-1
16.1 cluster-md-kmp-64kb +74 6.12.0-160100.9.1 openSUSE-SU-2026:22309-1
16.1 kernel-default-base 6.12.0-160100.9.1.160100.3.14 openSUSE-SU-2026:22309-1

ubuntu 4 releases · 49 packages

fixed 67 affected 2
linux-nvidia-tegra-5-15 linux-ibm-5-15 linux-intel-iotg-5-15 linux-oracle-5-15 linux-aws-5-15 linux-gcp-5-15 +43
ubuntu fixes for CVE-2026-74331
ReleasePackageFixed in
20.04-ESM linux-nvidia-tegra-5-15 5.15.0-1070.72~20.04.1
20.04-ESM linux-ibm-5-15 +1 5.15.0-1111.115~20.04.1
20.04-ESM linux-intel-iotg-5-15 5.15.0-1112.118~20.04.1
20.04-ESM linux-oracle-5-15 5.15.0-1114.120~20.04.1
20.04-ESM linux-aws-5-15 5.15.0-1117.124~20.04.1
20.04-ESM linux-gcp-5-15 5.15.0-1118.128~20.04.1

63 more rows

References

Show all 40 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.