CVE-2022-49446 json
nvdimm: Fix firmware activation deadlock scenarios
published 2025-02-26 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2022-54783
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
nvdimm: Fix firmware activation deadlock scenarios
Lockdep reports the following deadlock scenarios for CXL root device power-management, device_prepare(), operations, and device_shutdown() operations for 'nd_region' devices:
Chain exists of: &nvdimm_region_key --> &nvdimm_bus->reconfig_mutex --> system_transition_mutex
Possible unsafe locking scenario:
CPU0 CPU1 ---- ---- lock(system_transition_mutex); lock(&nvdimm_bus->reconfig_mutex); lock(system_transition_mutex); lock(&nvdimm_region_key);
Chain exists of: &cxl_nvdimm_bridge_key --> acpi_scan_lock --> &cxl_root_key
Possible unsafe locking scenario:
CPU0 CPU1 ---- ---- lock(&cxl_root_key); lock(acpi_scan_lock); lock(&cxl_root_key); lock(&cxl_nvdimm_bridge_key);
These stem from holding nvdimm_bus_lock() over hibernate_quiet_exec() which walks the entire system device topology taking device_lock() along the way. The nvdimm_bus_lock() is protecting against unregistration, multiple simultaneous ops callers, and preventing activate_show() from racing activate_store(). For the first 2, the lock is redundant. Unregistration already flushes all ops users, and sysfs already prevents multiple threads to be active in an ops handler at the same time. For the last userspace should already be waiting for its last activate_store() to complete, and does not need activate_show() to flush the write side, so this lock usage can be deleted in these attributes.
Patch / fix
- Linux Linux 5.10.121, 5.15.46, 5.17.14, 5.18.3, 5.19
- linux Debian 14, Debian 13, Debian 12 5.18.5-1
debian advisories DEBIAN-CVE-2022-49446
- linux Ubuntu 22.04 LTS 5.15.0-47.51
- linux-aws Ubuntu 22.04 LTS 5.15.0-1019.23
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1017.23
- linux-gke Ubuntu 22.04 LTS 5.15.0-1015.18
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1013.15
- linux-kvm Ubuntu 22.04 LTS 5.15.0-1017.21
- linux-azure Ubuntu 22.04 LTS 5.15.0-1019.24
- linux-gkeop Ubuntu 22.04 LTS 5.15.0-1002.4
ubuntu advisories UBUNTU-CVE-2022-49446
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-64kb SLES 15 SP3-LTSS, SLE High Performance Computing 15 SP3-LTSS, Enterprise Storage 7.1 5.3.18-150300.59.201.1
- kernel-syms SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE High Performance Computing 15 SP3-LTSS +1 more 5.3.18-150300.59.201.1
- kernel-source SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE High Performance Computing 15 SP3-LTSS +1 more 5.3.18-150300.59.201.1
- kernel-default SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE Micro 5.2 +5 more 5.3.18-150300.59.201.1
- kernel-preempt SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE High Performance Computing 15 SP3-LTSS +1 more 5.3.18-150300.59.201.1
- kernel-obs-build SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE High Performance Computing 15 SP3-LTSS +1 more 5.3.18-150300.59.201.1
- kernel-default-base SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE Micro 5.2 +3 more 5.3.18-150300.59.201.1.150300.18.120.1
- kernel-64kb SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS, SLE High Performance Computing 15 SP5-ESPOS 5.14.21-150500.55.100.1
suse advisories SUSE-SU-2025:1263-1SUSE-SU-2025:1241-1SUSE-SU-2025:1194-1SUSE-SU-2025:1176-1
- git.kernel.org/stable/c/641649f31e20df630310f5c22f26c071acc676d4 commit
- git.kernel.org/stable/c/2f97ebc58d5fc83ca1528cd553fa725472ab3ca8 commit
- git.kernel.org/stable/c/ceb924ee16b2c8e48dcac3d9ad6be01c40b5a228 commit
- git.kernel.org/stable/c/2fd853fdb40afc052de338693df1372f2ead7be7 commit
- git.kernel.org/stable/c/e6829d1bd3c4b58296ee9e412f7ed4d6cb390192 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-49446 updated cvss 5.5
kernel: nvdimm: Fix firmware activation deadlock scenarios
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 13 mo ago
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-667 Improper Locking
- Technology feeds
References
-
git.kernel.org
/stable/c/641649f31e20df630310f5c22f26c071acc676d4
patch
-
git.kernel.org
/stable/c/2f97ebc58d5fc83ca1528cd553fa725472ab3ca8
patch
-
git.kernel.org
/stable/c/ceb924ee16b2c8e48dcac3d9ad6be01c40b5a228
patch
-
git.kernel.org
/stable/c/2fd853fdb40afc052de338693df1372f2ead7be7
patch
-
git.kernel.org
/stable/c/e6829d1bd3c4b58296ee9e412f7ed4d6cb390192
patch
Sources
- CVE List CVE-2022-49446
- NVD CVE-2022-49446
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.