CVE-2026-93098

/// Technical description

In the Linux kernel, the following vulnerability has been resolved:

rpmsg: glink: fix deadlock in endpoint destroy during driver detach

During driver detach, the device core holds the device mutex throughout

the driver's remove callback chain. When the rpmsg endpoint is

destroyed as part of that teardown, the GLINK endpoint destroy

implementation attempts to unregister the underlying rpmsg device.

That unregistration calls device_del(), which tries to re-acquire the

same device mutex already held higher up the stack, causing rmmod to

hang indefinitely.

The deadlock manifests with the following call chain:

[<0>] device_del+0x44/0x414  <- tries to acquire same mutex

[<0>] device_unregister+0x18/0x34

[<0>] rpmsg_unregister_device+0x28/0x4c

[<0>] qcom_glink_remove_rpmsg_device+0x70/0xc0

[<0>] qcom_glink_destroy_ept+0x58/0xbc

[<0>] rpmsg_dev_remove+0x50/0x60

[<0>] device_remove+0x4c/0x80

[<0>] device_release_driver_internal+0x1cc/0x228 <- acquires device mutex

[<0>] driver_detach+0x4c

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