CVE-2022-50149

/// Technical 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(

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References