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-2022-50149

kernel: driver core: fix potential deadlock in __driver_attach

Overview

Published
18 Jun 2025
Modified
17 Jun 2026
Medium CVE
0 Registry packages
131 OS packages
9 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

5.5 · MEDIUM

CVSS 3.1 base score, scored by NVD.

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

Weakness: CWE-667

Affected packages · 0

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

Operating systems · 98 fixes

Photon OS 1 release · 1 package

fixed 1
bpftool
Photon OS fixes for CVE-2022-50149
ReleasePackageFixed in
4.0 bpftool +9 5.10.46-2.ph4

Red Hat 2 releases · 3 packages

affected 2 fixed 3
kernel-rt bpftool kernel
Red Hat fixes for CVE-2022-50149
ReleasePackageFixed inAdvisory
8 kernel-rt +14 affected —
8 bpftool +22 0:4.18.0-477.10.1.el8_8 RHSA-2023:2951
9 kernel-rt +20 affected —
9 kernel +44 0:5.14.0-284.11.1.el9_2 RHSA-2023:2458
9 bpftool 0:7.0.0-284.11.1.el9_2 RHSA-2023:2458

SUSE Linux Enterprise 3 releases · 5 packages

fixed 8
kgraft-patch-4-12-14-122-269-default cluster-md-kmp-default kernel-devel kernel-default-base kernel-livepatch-5-14-21-150500-55-113-default
SUSE Linux Enterprise fixes for CVE-2022-50149
ReleasePackageFixed inAdvisory
12.5 kgraft-patch-4-12-14-122-269-default 1-8.3.1 SUSE-SU-2025:02846-1
12.5 cluster-md-kmp-default +13 4.12.14-122.269.1 SUSE-SU-2025:02846-1
15.4 kernel-devel +4 5.14.21-150400.24.170.1 SUSE-SU-2025:02537-1
15.4 cluster-md-kmp-default +10 5.14.21-150400.24.170.2 SUSE-SU-2025:02537-1
15.4 kernel-default-base 5.14.21-150400.24.170.2.150400.24.86.2 SUSE-SU-2025:02537-1
15.5 kernel-livepatch-5-14-21-150500-55-113-default 1-150500.11.3.1 SUSE-SU-2025:02264-1

2 more rows

SUSE Linux Enterprise Micro 5 releases · 4 packages

fixed 16
kernel-rt kernel-default kernel-default-base kernel-devel-rt
SUSE Linux Enterprise Micro fixes for CVE-2022-50149
ReleasePackageFixed inAdvisory
5.1 kernel-rt +1 5.3.18-150300.214.1 SUSE-SU-2025:02320-1
5.1 kernel-default 5.3.18-150300.59.211.1 SUSE-SU-2025:02308-1
5.1 kernel-default-base 5.3.18-150300.59.211.1.150300.18.126.1 SUSE-SU-2025:02308-1
5.2 kernel-rt +1 5.3.18-150300.214.1 SUSE-SU-2025:02320-1
5.2 kernel-default 5.3.18-150300.59.211.1 SUSE-SU-2025:02308-1
5.2 kernel-default-base 5.3.18-150300.59.211.1.150300.18.126.1 SUSE-SU-2025:02308-1

10 more rows

debian 4 releases · 1 package

fixed 4
linux
debian fixes for CVE-2022-50149
ReleasePackageFixed in
11 linux 5.10.140-1
12 linux 6.0.2-1
13 linux 6.0.2-1
14 linux 6.0.2-1

echo 1 release · 1 package

fixed 1
linux
echo fixes for CVE-2022-50149
ReleasePackageFixed in
linux 6.0.2-1

root.io debian 3 releases · 1 package

fixed 3
rootio-linux
root.io debian fixes for CVE-2022-50149
ReleasePackageFixed in
11 rootio-linux 5.10.140-1
12 rootio-linux 6.0.2-1
13 rootio-linux 6.0.2-1

root.io ubuntu 1 release · 1 package

fixed 1
rootio-linux
root.io ubuntu fixes for CVE-2022-50149
ReleasePackageFixed in
22.04 rootio-linux 5.15.0-53.59

ubuntu 5 releases · 28 packages

fixed 59
linux-ibm-5-4 linux-raspi-5-4 linux-oracle-5-4 linux-aws-5-4 linux-gcp-5-4 linux-azure-5-4 +22
ubuntu fixes for CVE-2022-50149
ReleasePackageFixed in
18.04 linux-ibm-5-4 5.4.0-1037.42~18.04.1
18.04 linux-raspi-5-4 5.4.0-1074.85~18.04.1
18.04 linux-oracle-5-4 5.4.0-1087.96~18.04.1
18.04 linux-aws-5-4 5.4.0-1089.97~18.04.1
18.04 linux-gcp-5-4 5.4.0-1093.102~18.04.1
18.04 linux-azure-5-4 5.4.0-1095.101~18.04.1

53 more rows

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.