CVE-2026-93098 Affecting kernel-uek-modules-usb package, versions <0:6.12.0-207.111.5.1.el10uek
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ORACLE10-KERNELUEKMODULESUSB-20583415
- published8 Oct 2026
- disclosed17 Sept 2026
Introduced: 17 Sep 2026
CVE-2026-93098 (opens in a new tab)How to fix?
Upgrade Oracle:10 kernel-uek-modules-usb to version 0:6.12.0-207.111.5.1.el10uek or higher.
This issue was patched in ELSA-2026-500374.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-uek-modules-usb package and not the kernel-uek-modules-usb package as distributed by Oracle.
See How to fix? for Oracle:10 relevant fixed versions and status.
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.
References
- https://linux.oracle.com/cve/CVE-2026-93098.html
- https://linux.oracle.com/errata/ELSA-2026-500374.html
- https://git.kernel.org/stable/c/48f55b90f0d713e477e26b85d7327d9592d016f9
- https://git.kernel.org/stable/c/5a5a48e788e02fd8a8eb7188ce440572d6c12418
- https://git.kernel.org/stable/c/73092c2292aa65515671e54abbcda2166d3827ed
- https://git.kernel.org/stable/c/8597f669a5268e0dcf243e2b2d6ca00370117057
- https://git.kernel.org/stable/c/bbc236357876d35a624030e5c50eedbc380be98e
- https://git.kernel.org/stable/c/cbcdf96e1c87bc07055d04264018ded1f3bafffb
- https://git.kernel.org/stable/c/e559626bee8a6632aafc08eedcdb4bf26ca245c5
- https://git.kernel.org/stable/c/ecad679e2b92c419cc22cc8f257cd457d5192647