Module-removal hang via recursive device mutex acquisition
Published Sep 17, 2026 · Updated Sep 17, 2026
Linux's GLINK endpoint teardown deadlock allows local users to hang module removal indefinitely by detaching an rpmsg driver. The qcom_glink_destroy_ept function redundantly unregisters the rpmsg device, causing device_del to acquire a device mutex already held by the driver-detach path. The reported FastRPC removal path requires module-removal privileges and GLINK-backed rpmsg teardown; the documented consequence is a stuck removal operation, not a demonstrated system-wide crash.
Summary
What happened
Linux's GLINK endpoint teardown deadlock allows local users to hang module removal indefinitely by detaching an rpmsg driver. The qcom_glink_destroy_ept function redundantly unregisters the rpmsg device, causing device_del to acquire a device mutex already held by the driver-detach path. The reported FastRPC removal path requires module-removal privileges and GLINK-backed rpmsg teardown; the documented consequence is a stuck removal operation, not a demonstrated system-wide crash.
The record
- CVE
- CVE-2026-93098
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=24fd02c3a4798de7dc94b55d36a1685fe6cdaf69 <bbc236357876d35a624030e5c50eedbc380be98e
- Affected versionversion=32fe8cdf541863239b81c80b8b04112d6e8792cf <8597f669a5268e0dcf243e2b2d6ca00370117057
- Affected versionversion=5.10.248 <5.10.270
- Affected versionversion=5.15.198 <5.15.221
- Affected versionversion=6.1.160 <6.1.188
- Affected versionversion=6.12.64 <6.12.110
- Affected versionversion=6.18.3 <6.18.52
- Affected versionversion=6.19
- Affected versionversion=6.6.120 <6.6.157
- Affected versionversion=93b6b9e4acff4794e7426d3ad64ef14e3b3e8919 <73092c2292aa65515671e54abbcda2166d3827ed
- Affected versionversion=a53e356df548f6b0e82529ef3cc6070f42622189 <5a5a48e788e02fd8a8eb7188ce440572d6c12418
- Affected versionversion=a53e356df548f6b0e82529ef3cc6070f42622189 <e559626bee8a6632aafc08eedcdb4bf26ca245c5
- Affected versionversion=c6210714347f72bae8e7142dc0a7f99923c466e7 <48f55b90f0d713e477e26b85d7327d9592d016f9
- Affected versionversion=f80e4e91b010ee7d6c52f24d069975ac955ac6b2 <ecad679e2b92c419cc22cc8f257cd457d5192647
- Affected versionversion=fcab5c2672f8dac3d77013dbe047b2441f4141f5 <cbcdf96e1c87bc07055d04264018ded1f3bafffb
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started