CVE-2026-93098— Linux内核 glink 驱动资源释放死锁漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Linux 内核中，已解决以下漏洞： rpmsg: glink: 修复驱动分离时端点销毁过程中的死锁问题 在驱动分离（driver detach）期间，设备核心在整个驱动的 回调链中持有设备互斥量（device mutex）。当 rpmsg 端点作为该清理过程的一部分被销毁时，GLINK 端点销毁实现会尝试注销（unregister）底层的 rpmsg 设备。该注销操作调用了 ，而 试图重新获取已在调用栈上层持有的同一设备互斥量，从而导致 （移除内核模块）无限挂起。 该死锁通过以下调用链显现： 端点销毁过程中的
可能的 ATT&CK 技术 1 AI
T1499 · Endpoint Denial of Service影响版本矩阵 24
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 93b6b9e4acff4794e7426d3ad64ef14e3b3e8919< 73092c2292aa65515671e54abbcda2166d3827ed |
affected |
24fd02c3a4798de7dc94b55d36a1685fe6cdaf69< bbc236357876d35a624030e5c50eedbc380be98e |
affected | ||
32fe8cdf541863239b81c80b8b04112d6e8792cf< 8597f669a5268e0dcf243e2b2d6ca00370117057 |
affected | ||
c6210714347f72bae8e7142dc0a7f99923c466e7< 48f55b90f0d713e477e26b85d7327d9592d016f9 |
affected | ||
fcab5c2672f8dac3d77013dbe047b2441f4141f5< cbcdf96e1c87bc07055d04264018ded1f3bafffb |
affected | ||
f80e4e91b010ee7d6c52f24d069975ac955ac6b2< ecad679e2b92c419cc22cc8f257cd457d5192647 |
affected | ||
a53e356df548f6b0e82529ef3cc6070f42622189< e559626bee8a6632aafc08eedcdb4bf26ca245c5 |
affected | ||
a53e356df548f6b0e82529ef3cc6070f42622189< 5a5a48e788e02fd8a8eb7188ce440572d6c12418 |
affected | ||
| … +16 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-93098 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
rpmsg: glink: fix deadlock in endpoint destroy during driver detach
来源: CVE Program / CVE List V5
Vulnerability 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/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.
来源: CVE Program / CVE List V5
CVSS Information
N/A
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
受影响产品
二、漏洞 CVE-2026-93098 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-93098 的情报信息
请登录查看更多情报信息。
CVE-2026-93098 补丁与修复 (8)
同批安全公告 · Linux · 2026-09-17 · 共 600 条
| CVE-2026-92489 | 9.8 CRITICAL | Linux内核 xfrm 双重释放漏洞 |
| CVE-2026-90173 | 9.8 CRITICAL | SMB SmbDirect 释放完成队列漏洞 |
| CVE-2026-90235 | 9.8 CRITICAL | 内核sunrpc xprtsock并发读取修复 |
| CVE-2026-90104 | 9.8 CRITICAL | NFSv4.1 解码前未清空调用列表 |
| CVE-2026-90151 | 9.8 CRITICAL | NFSv4客户端分配失败回调处理漏洞 |
| CVE-2026-90110 | 9.4 CRITICAL | inetpeer 随机化RB树节点比较 |
| CVE-2026-90230 | 9.1 CRITICAL | Linux内核Nvme-target堆越界读取漏洞 |
| CVE-2026-90414 | 9.1 CRITICAL | IB/isert拒绝声明超出实际接收数据的PDU |
| CVE-2026-90413 | 9.1 CRITICAL | IB/isert 登录PDU数据长度校验漏洞 |
| CVE-2026-90367 | 8.8 HIGH | Linux内核MT7996驱动死锁漏洞 |
| CVE-2026-90329 | 8.8 HIGH | Linux 内核 HID 驱动探测清理同步漏洞 |
| CVE-2026-93189 | 8.8 HIGH | Linux HID核心使用已释放内存漏洞 |
| CVE-2026-90286 | 8.8 HIGH | AMDGPU GFX6 计算队列PFP使用漏洞 |
| CVE-2026-90357 | 8.8 HIGH | mt76驱动MT7915无线局域网远程拒绝服务漏洞 |
| CVE-2026-90240 | 8.8 HIGH | Linux内核 IOMMU 别名拆除时刷新缓存错误 |
| CVE-2026-93042 | 8.8 HIGH | Linux内核dmaengine模块资源耗尽漏洞 |
| CVE-2026-90256 | 8.8 HIGH | Linux Bluetooth L2CAP 远程代码执行漏洞 |
| CVE-2026-90380 | 8.8 HIGH | MT76驱动 mt792x 使用释放后内存漏洞 |
| CVE-2026-90381 | 8.8 HIGH | Linux内核mt76驱动无线信道切换漏洞 |
| CVE-2026-90425 | 8.8 HIGH | Linux内核 5.x 内核漏洞 |
显示前 20 条，共 600 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-93098
暂无评论