GHSA-RMPV-CFQV-CMJX
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In 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/0x98 [<0>] bus_remove_driver+0x6c/0xbc [<0>] driver_unregister+0x30/0x60 [<0>] unregister_rpmsg_driver+0x10/0x1c [<0>] fastrpc_exit+0x28/0x38 [fastrpc] [<0>] __arm64_sys_delete_module+0x1b8/0x294 [<0>] invoke_syscall+0x48/0x10c [<0>] el0_svc_common.constprop.0+0xc0/0xe0 [<0>] do_el0_svc+0x1c/0x28 [<0>] el0_svc+0x34/0x108 [<0>] el0t_64_sync_handler+0xa0/0xe4 [<0>] el0t_64_sync+0x198/0x19c
The rpmsg device unregistration inside endpoint destroy is redundant. In both contexts where endpoint destruction is triggered:
-
Driver detach path: the driver core already tears down the rpmsg device.
-
Channel close path: the rpmsg device is already unregistered before endpoint destruction is reached.
Remove the redundant unregistration to fix the deadlock.
{
"affected": [],
"aliases": [
"CVE-2026-93098"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:18:03Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nrpmsg: glink: fix deadlock in endpoint destroy during driver detach\n\nDuring driver detach, the device core holds the device mutex throughout\nthe driver\u0027s remove callback chain. When the rpmsg endpoint is\ndestroyed as part of that teardown, the GLINK endpoint destroy\nimplementation attempts to unregister the underlying rpmsg device.\nThat unregistration calls device_del(), which tries to re-acquire the\nsame device mutex already held higher up the stack, causing rmmod to\nhang indefinitely.\n\nThe deadlock manifests with the following call chain:\n\n[\u003c0\u003e] device_del+0x44/0x414\u2003\u2003\u003c- tries to acquire same mutex\n[\u003c0\u003e] device_unregister+0x18/0x34\n[\u003c0\u003e] rpmsg_unregister_device+0x28/0x4c\n[\u003c0\u003e] qcom_glink_remove_rpmsg_device+0x70/0xc0\n[\u003c0\u003e] qcom_glink_destroy_ept+0x58/0xbc\n[\u003c0\u003e] rpmsg_dev_remove+0x50/0x60\n[\u003c0\u003e] device_remove+0x4c/0x80\n[\u003c0\u003e] device_release_driver_internal+0x1cc/0x228 \u003c- acquires device mutex\n[\u003c0\u003e] driver_detach+0x4c/0x98\n[\u003c0\u003e] bus_remove_driver+0x6c/0xbc\n[\u003c0\u003e] driver_unregister+0x30/0x60\n[\u003c0\u003e] unregister_rpmsg_driver+0x10/0x1c\n[\u003c0\u003e] fastrpc_exit+0x28/0x38 [fastrpc]\n[\u003c0\u003e] __arm64_sys_delete_module+0x1b8/0x294\n[\u003c0\u003e] invoke_syscall+0x48/0x10c\n[\u003c0\u003e] el0_svc_common.constprop.0+0xc0/0xe0\n[\u003c0\u003e] do_el0_svc+0x1c/0x28\n[\u003c0\u003e] el0_svc+0x34/0x108\n[\u003c0\u003e] el0t_64_sync_handler+0xa0/0xe4\n[\u003c0\u003e] el0t_64_sync+0x198/0x19c\n\nThe rpmsg device unregistration inside endpoint destroy is redundant.\nIn both contexts where endpoint destruction is triggered:\n\n- Driver detach path: the driver core already tears down the rpmsg\n device.\n\n- Channel close path: the rpmsg device is already unregistered before\n endpoint destruction is reached.\n\nRemove the redundant unregistration to fix the deadlock.",
"id": "GHSA-rmpv-cfqv-cmjx",
"modified": "2026-09-17T18:32:10Z",
"published": "2026-09-17T18:32:10Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93098"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/48f55b90f0d713e477e26b85d7327d9592d016f9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5a5a48e788e02fd8a8eb7188ce440572d6c12418"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/73092c2292aa65515671e54abbcda2166d3827ed"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8597f669a5268e0dcf243e2b2d6ca00370117057"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bbc236357876d35a624030e5c50eedbc380be98e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/cbcdf96e1c87bc07055d04264018ded1f3bafffb"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e559626bee8a6632aafc08eedcdb4bf26ca245c5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ecad679e2b92c419cc22cc8f257cd457d5192647"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.