Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-49446nvdimm: Fix firmware activation deadlock scenarios

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 15 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-49446, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 48001ea50d17f3eb06a552e9ecf21f7fc01b25da – < 641649f31e20df630310f5c22f26c071acc676d4
    • affected 48001ea50d17f3eb06a552e9ecf21f7fc01b25da – < 2f97ebc58d5fc83ca1528cd553fa725472ab3ca8
    • affected 48001ea50d17f3eb06a552e9ecf21f7fc01b25da – < ceb924ee16b2c8e48dcac3d9ad6be01c40b5a228
    • affected 48001ea50d17f3eb06a552e9ecf21f7fc01b25da – < 2fd853fdb40afc052de338693df1372f2ead7be7
    • affected 48001ea50d17f3eb06a552e9ecf21f7fc01b25da – < e6829d1bd3c4b58296ee9e412f7ed4d6cb390192
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 5.10.121 – ≤ 5.10.*
    • unaffected 5.15.46 – ≤ 5.15.*
    • unaffected 5.17.14 – ≤ 5.17.*
    • unaffected 5.18.3 – ≤ 5.18.*
    • unaffected 5.19 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49446 badge
[![CVE-2022-49446](https://cveledger.app/badge/CVE-2022-49446.svg)](https://cveledger.app/cve/CVE-2022-49446)

Record last updated .