LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50149: driver core: fix potential deadlock in __driver_attach

In the Linux kernel, the following vulnerability has been resolved: driver core: fix potential deadlock in __driver_attach In __driver_attach function, There are also AA deadlock problem, like the commit b232b02bf3c2 ("driver core: fix deadlock in __device_attach"). stack like commit b232b02bf3c2 ("driver core: fix deadlock in __device_attach"). list below: In __driver_attach function, The lock holding logic is as follows: ... __driver_attach if (driver_allows_async_probing(drv)) device_lock(dev) // get lock dev async_schedule_dev(__driver_attach_async_helper, dev); // func async_schedule_node async_schedule_node_domain(func) entry = kzalloc(sizeof(struct async_entry), GFP_ATOMIC); /* when fail or work limit, sync to execute func, but __driver_attach_async_helper will get lock dev as will, which will lead to A-A deadlock. */ if (!entry || atomic_read(&entry_count) > MAX_WORK) { func; else queue_work_node(node, system_unbound_wq, &entry->work) device_unlock(dev) As above show, when it is allowed to do async probes, because of out of memory or work limit, async work is not be allowed, to do sync execute instead. it will lead to A-A deadlock because of __driver_attach_async_helper getting lock dev. Reproduce: and it can be reproduce by make the condition (if (!entry || atomic_read(&entry_count) > MAX_WORK)) untenable, like below: [ 370.785650] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 370.787154] task:swapper/0 state:D stack: 0 pid: 1 ppid: 0 flags:0x00004000 [ 370.788865] Call Trace: [ 370.789374] <TASK> [ 370.789841] __schedule+0x482/0x1050 [ 370.790613] schedule+0x92/0x1a0 [ 370.791290] schedule_preempt_disabled+0x2c/0x50 [ 370.792256] __mutex_lock.isra.0+0x757/0xec0 [ 370.793158] __mutex_lock_slowpath+0x1f/0x30 [ 370.794079] mutex_lock+0x50/0x60 [ 370.794795] __device_driver_lock+0x2f/0x70 [ 370.795677] ? driver_probe_device+0xd0/0xd0 [ 370.796576] __driver_attach_async_helper+0x1d/0xd0 [ 370.797318] ? driver_probe_device+0xd0/0xd0 [ 370.797957] async_schedule_node_domain+0xa5/0xc0 [ 370.798652] async_schedule_node+0x19/0x30 [ 370.799243] __driver_attach+0x246/0x290 [ 370.799828] ? driver_allows_async_probing+0xa0/0xa0 [ 370.800548] bus_for_each_dev+0x9d/0x130 [ 370.801132] driver_attach+0x22/0x30 [ 370.801666] bus_add_driver+0x290/0x340 [ 370.802246] driver_register+0x88/0x140 [ 370.802817] ? virtio_scsi_init+0x116/0x116 [ 370.803425] scsi_register_driver+0x1a/0x30 [ 370.804057] init_sd+0x184/0x226 [ 370.804533] do_one_initcall+0x71/0x3a0 [ 370.805107] kernel_init_freeable+0x39a/0x43a [ 370.805759] ? rest_init+0x150/0x150 [ 370.806283] kernel_init+0x26/0x230 [ 370.806799] ret_from_fork+0x1f/0x30 To fix the deadlock, move the async_schedule_dev outside device_lock, as we can see, in async_schedule_node_domain, the parameter of queue_work_node is system_unbound_wq, so it can accept concurrent operations. which will also not change the code logic, and will not lead to deadlock.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50149 is a Linux kernel driver-core availability bug. Under specific driver attach conditions, the kernel can deadlock while handling asynchronous probing, potentially leaving a system hung. The provided sources do not give a CVSS score or evidence of active exploitation.

Executive priority

Treat as a maintenance-priority availability issue, not an emergency based on current evidence. Patch through normal kernel update channels, with faster handling for critical Linux systems where hangs would materially disrupt operations.

Technical view

The issue is an AA deadlock in __driver_attach. When async probing is allowed but async scheduling falls back to synchronous execution, __driver_attach_async_helper can attempt to reacquire a device lock already held by __driver_attach. Kernel stable commits resolve this by moving async_schedule_dev outside device_lock.

Likely exposure

Exposure is limited to systems running affected Linux kernel versions or vendor kernels containing the vulnerable driver-core logic. Highest concern is availability-sensitive Linux infrastructure, embedded systems, appliances, or custom kernels that lag stable fixes.

Exploitation context

The source describes a reproducible kernel hang condition but does not identify remote attack paths, privilege requirements, CVSS scoring, or active exploitation. KEV status is false in the provided bundle.

Researcher notes

Evidence is strongest for the root cause and upstream fix direction. The bundle lacks CVSS, CWE, affected distribution advisories, exploitability analysis, and proof of active exploitation, so exposure assessment requires local kernel lineage validation.

Mitigation direction

  • Map running kernels to vendor advisories and the listed stable commits.
  • Apply the relevant Linux kernel or distribution update when available.
  • Prioritize systems with strict uptime or boot reliability requirements.
  • For custom kernels, review whether the stable driver-core fix is present.

Validation and detection

  • Record kernel versions across Linux hosts and appliances.
  • Check vendor package changelogs for CVE-2022-50149 or the stable commit IDs.
  • Confirm patched kernels include the driver-core lock-order fix.
  • Review monitoring for unexplained kernel hangs during boot or driver probing.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50149 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxef0ff68351be4fd83bec2d797f0efdc0174a55a4, ef0ff68351be4fd83bec2d797f0efdc0174a55a4, ef0ff68351be4fd83bec2d797f0efdc0174a55a4, ef0ff68351be4fd83bec2d797f0efdc0174a55a4, ef0ff68351be4fd83bec2d797f0efdc0174a55a4, ef0ff68351be4fd83bec2d797f0efdc0174a55a4unaffected
LinuxLinux5.1, 0, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.