<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 13:47:31 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-93098</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-93098</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-93098</guid>
    </item>
    <item>
      <title>fkie_cve-2026-93098</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-93098</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rpmsg: glink: fix deadlock in endpoint destroy during driver detach&lt;/p&gt;
&lt;p&gt;During driver detach, the device core holds the device mutex throughout
the driver&amp;#39;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.&lt;/p&gt;
&lt;p&gt;The deadlock manifests with the following call chain:&lt;/p&gt;
&lt;p&gt;[&amp;lt;0&amp;gt;] device_del+0x44/0x414  &amp;lt;- tries to acquire same mutex
[&amp;lt;0&amp;gt;] device_unregister+0x18/0x34
[&amp;lt;0&amp;gt;] rpmsg_unregister_device+0x28/0x4c
[&amp;lt;0&amp;gt;] qcom_glink_remove_rpmsg_device+0x70/0xc0
[&amp;lt;0&amp;gt;] qcom_glink_destroy_ept+0x58/0xbc
[&amp;lt;0&amp;gt;] rpmsg_dev_remove+0x50/0x60
[&amp;lt;0&amp;gt;] device_remove+0x4c/0x80
[&amp;lt;0&amp;gt;] device_release_driver_internal+0x1cc/0x228  &amp;lt;- acquires device mutex
[&amp;lt;0&amp;gt;] driver_detach+0x4c/0x98
[&amp;lt;0&amp;gt;] bus_remove_driver+0x6c/0xbc
[&amp;lt;0&amp;gt;] driver_unregister+0x30/0x60
[&amp;lt;0&amp;gt;] unregister_rpmsg_driver+0x10/0x1c
[&amp;lt;0&amp;gt;] fastrpc_exit+0x28/0x38 [fastrpc]
[&amp;lt;0&amp;gt;] __arm64_sys_delete_module+0x1b8/0x294
[&amp;lt;0&amp;gt;] invoke_syscall+0x48/0x10c
[&amp;lt;0&amp;gt;] el0_svc_common.constprop.0+0xc0/0xe0
[&amp;lt;0&amp;gt;] do_el0_svc+0x1c/0x28
[&amp;lt;0&amp;gt;] el0_svc+0x34/0x108
[&amp;lt;0&amp;gt;] el0t_64_sync_handler+0xa0/0xe4
[&amp;lt;0&amp;gt;] el0t_64_sync+0x198/0x19c&lt;/p&gt;
&lt;p&gt;The rpmsg device unregistration inside endpoint destroy is redundant.
In both contexts where endpoint dest…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rpmsg: glink: fix deadlock in endpoint destroy during driver detach&lt;/p&gt;
&lt;p&gt;During driver detach, the device core holds the device mutex throughout
the driver&amp;#39;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.&lt;/p&gt;
&lt;p&gt;The deadlock manifests with the following call chain:&lt;/p&gt;
&lt;p&gt;[&amp;lt;0&amp;gt;] device_del+0x44/0x414  &amp;lt;- tries to acquire same mutex
[&amp;lt;0&amp;gt;] device_unregister+0x18/0x34
[&amp;lt;0&amp;gt;] rpmsg_unregister_device+0x28/0x4c
[&amp;lt;0&amp;gt;] qcom_glink_remove_rpmsg_device+0x70/0xc0
[&amp;lt;0&amp;gt;] qcom_glink_destroy_ept+0x58/0xbc
[&amp;lt;0&amp;gt;] rpmsg_dev_remove+0x50/0x60
[&amp;lt;0&amp;gt;] device_remove+0x4c/0x80
[&amp;lt;0&amp;gt;] device_release_driver_internal+0x1cc/0x228  &amp;lt;- acquires device mutex
[&amp;lt;0&amp;gt;] driver_detach+0x4c/0x98
[&amp;lt;0&amp;gt;] bus_remove_driver+0x6c/0xbc
[&amp;lt;0&amp;gt;] driver_unregister+0x30/0x60
[&amp;lt;0&amp;gt;] unregister_rpmsg_driver+0x10/0x1c
[&amp;lt;0&amp;gt;] fastrpc_exit+0x28/0x38 [fastrpc]
[&amp;lt;0&amp;gt;] __arm64_sys_delete_module+0x1b8/0x294
[&amp;lt;0&amp;gt;] invoke_syscall+0x48/0x10c
[&amp;lt;0&amp;gt;] el0_svc_common.constprop.0+0xc0/0xe0
[&amp;lt;0&amp;gt;] do_el0_svc+0x1c/0x28
[&amp;lt;0&amp;gt;] el0_svc+0x34/0x108
[&amp;lt;0&amp;gt;] el0t_64_sync_handler+0xa0/0xe4
[&amp;lt;0&amp;gt;] el0t_64_sync+0x198/0x19c&lt;/p&gt;
&lt;p&gt;The rpmsg device unregistration inside endpoint destroy is redundant.
In both contexts where endpoint dest…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-93098</guid>
    </item>
    <item>
      <title>GHSA-rmpv-cfqv-cmjx</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-rmpv-cfqv-cmjx</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rpmsg: glink: fix deadlock in endpoint destroy during driver detach&lt;/p&gt;
&lt;p&gt;During driver detach, the device core holds the device mutex throughout
the driver&amp;#39;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.&lt;/p&gt;
&lt;p&gt;The deadlock manifests with the following call chain:&lt;/p&gt;
&lt;p&gt;[&amp;lt;0&amp;gt;] device_del+0x44/0x414  &amp;lt;- tries to acquire same mutex
[&amp;lt;0&amp;gt;] device_unregister+0x18/0x34
[&amp;lt;0&amp;gt;] rpmsg_unregister_device+0x28/0x4c
[&amp;lt;0&amp;gt;] qcom_glink_remove_rpmsg_device+0x70/0xc0
[&amp;lt;0&amp;gt;] qcom_glink_destroy_ept+0x58/0xbc
[&amp;lt;0&amp;gt;] rpmsg_dev_remove+0x50/0x60
[&amp;lt;0&amp;gt;] device_remove+0x4c/0x80
[&amp;lt;0&amp;gt;] device_release_driver_internal+0x1cc/0x228  &amp;lt;- acquires device mutex
[&amp;lt;0&amp;gt;] driver_detach+0x4c/0x98
[&amp;lt;0&amp;gt;] bus_remove_driver+0x6c/0xbc
[&amp;lt;0&amp;gt;] driver_unregister+0x30/0x60
[&amp;lt;0&amp;gt;] unregister_rpmsg_driver+0x10/0x1c
[&amp;lt;0&amp;gt;] fastrpc_exit+0x28/0x38 [fastrpc]
[&amp;lt;0&amp;gt;] __arm64_sys_delete_module+0x1b8/0x294
[&amp;lt;0&amp;gt;] invoke_syscall+0x48/0x10c
[&amp;lt;0&amp;gt;] el0_svc_common.constprop.0+0xc0/0xe0
[&amp;lt;0&amp;gt;] do_el0_svc+0x1c/0x28
[&amp;lt;0&amp;gt;] el0_svc+0x34/0x108
[&amp;lt;0&amp;gt;] el0t_64_sync_handler+0xa0/0xe4
[&amp;lt;0&amp;gt;] el0t_64_sync+0x198/0x19c&lt;/p&gt;
&lt;p&gt;The rpmsg device unregistration inside endpoint destroy is redundant.
In both contexts where endpoint dest…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rpmsg: glink: fix deadlock in endpoint destroy during driver detach&lt;/p&gt;
&lt;p&gt;During driver detach, the device core holds the device mutex throughout
the driver&amp;#39;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.&lt;/p&gt;
&lt;p&gt;The deadlock manifests with the following call chain:&lt;/p&gt;
&lt;p&gt;[&amp;lt;0&amp;gt;] device_del+0x44/0x414  &amp;lt;- tries to acquire same mutex
[&amp;lt;0&amp;gt;] device_unregister+0x18/0x34
[&amp;lt;0&amp;gt;] rpmsg_unregister_device+0x28/0x4c
[&amp;lt;0&amp;gt;] qcom_glink_remove_rpmsg_device+0x70/0xc0
[&amp;lt;0&amp;gt;] qcom_glink_destroy_ept+0x58/0xbc
[&amp;lt;0&amp;gt;] rpmsg_dev_remove+0x50/0x60
[&amp;lt;0&amp;gt;] device_remove+0x4c/0x80
[&amp;lt;0&amp;gt;] device_release_driver_internal+0x1cc/0x228  &amp;lt;- acquires device mutex
[&amp;lt;0&amp;gt;] driver_detach+0x4c/0x98
[&amp;lt;0&amp;gt;] bus_remove_driver+0x6c/0xbc
[&amp;lt;0&amp;gt;] driver_unregister+0x30/0x60
[&amp;lt;0&amp;gt;] unregister_rpmsg_driver+0x10/0x1c
[&amp;lt;0&amp;gt;] fastrpc_exit+0x28/0x38 [fastrpc]
[&amp;lt;0&amp;gt;] __arm64_sys_delete_module+0x1b8/0x294
[&amp;lt;0&amp;gt;] invoke_syscall+0x48/0x10c
[&amp;lt;0&amp;gt;] el0_svc_common.constprop.0+0xc0/0xe0
[&amp;lt;0&amp;gt;] do_el0_svc+0x1c/0x28
[&amp;lt;0&amp;gt;] el0_svc+0x34/0x108
[&amp;lt;0&amp;gt;] el0t_64_sync_handler+0xa0/0xe4
[&amp;lt;0&amp;gt;] el0t_64_sync+0x198/0x19c&lt;/p&gt;
&lt;p&gt;The rpmsg device unregistration inside endpoint destroy is redundant.
In both contexts where endpoint dest…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-rmpv-cfqv-cmjx</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11893-1 — kernel-devel-7.2.8-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11893-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.8-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.8-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11893-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-93098</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93098</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 189 more&lt;/p&gt;
&lt;p&gt;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&amp;#39;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: [&amp;lt;0&amp;gt;] device_del+0x44/0x414  &amp;lt;- tries to acquire same mutex [&amp;lt;0&amp;gt;] device_unregister+0x18/0x34 [&amp;lt;0&amp;gt;] rpmsg_unregister_device+0x28/0x4c [&amp;lt;0&amp;gt;] qcom_glink_remove_rpmsg_device+0x70/0xc0 [&amp;lt;0&amp;gt;] qcom_glink_destroy_ept+0x58/0xbc [&amp;lt;0&amp;gt;] rpmsg_dev_remove+0x50/0x60 [&amp;lt;0&amp;gt;] device_remove+0x4c/0x80 [&amp;lt;0&amp;gt;] device_release_driver_internal+0x1cc/0x228  &amp;lt;- acquires device mutex [&amp;lt;0&amp;gt;] driver_detach+0x4c/0x98 [&amp;lt;0&amp;gt;] bus_remove_driver+0x6c/0xbc [&amp;lt;0&amp;gt;] driver_unregister+0x30/0x60 [&amp;lt;0&amp;gt;] unregister_rpmsg_driver+0x10/0x1c [&amp;lt;0&amp;gt;] fastrpc_exit+0x28/0x38 [fastrpc] [&amp;lt;0&amp;gt;] __arm64_sys_delete_module+0x1b8/0x294 [&amp;lt;0&amp;gt;] invoke_syscall+0x48/0x10c [&amp;lt;0&amp;gt;] el0_svc_common.constprop.0+0xc0/0xe0 [&amp;lt;0&amp;gt;] do_el0_svc+0x1c/0x28 [&amp;lt;0&amp;gt;] el0_svc+0x34/0x108 [&amp;lt;0&amp;gt;] el0t_64_sync_handler+0xa0/0xe4 [&amp;lt;0&amp;gt;] el0t_64_sync+0x198/0x19c The rpmsg device unregistration inside endpoint destroy is redundant. In both contexts where endpoint destructi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 189 more&lt;/p&gt;
&lt;p&gt;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&amp;#39;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: [&amp;lt;0&amp;gt;] device_del+0x44/0x414  &amp;lt;- tries to acquire same mutex [&amp;lt;0&amp;gt;] device_unregister+0x18/0x34 [&amp;lt;0&amp;gt;] rpmsg_unregister_device+0x28/0x4c [&amp;lt;0&amp;gt;] qcom_glink_remove_rpmsg_device+0x70/0xc0 [&amp;lt;0&amp;gt;] qcom_glink_destroy_ept+0x58/0xbc [&amp;lt;0&amp;gt;] rpmsg_dev_remove+0x50/0x60 [&amp;lt;0&amp;gt;] device_remove+0x4c/0x80 [&amp;lt;0&amp;gt;] device_release_driver_internal+0x1cc/0x228  &amp;lt;- acquires device mutex [&amp;lt;0&amp;gt;] driver_detach+0x4c/0x98 [&amp;lt;0&amp;gt;] bus_remove_driver+0x6c/0xbc [&amp;lt;0&amp;gt;] driver_unregister+0x30/0x60 [&amp;lt;0&amp;gt;] unregister_rpmsg_driver+0x10/0x1c [&amp;lt;0&amp;gt;] fastrpc_exit+0x28/0x38 [fastrpc] [&amp;lt;0&amp;gt;] __arm64_sys_delete_module+0x1b8/0x294 [&amp;lt;0&amp;gt;] invoke_syscall+0x48/0x10c [&amp;lt;0&amp;gt;] el0_svc_common.constprop.0+0xc0/0xe0 [&amp;lt;0&amp;gt;] do_el0_svc+0x1c/0x28 [&amp;lt;0&amp;gt;] el0_svc+0x34/0x108 [&amp;lt;0&amp;gt;] el0t_64_sync_handler+0xa0/0xe4 [&amp;lt;0&amp;gt;] el0t_64_sync+0x198/0x19c The rpmsg device unregistration inside endpoint destroy is redundant. In both contexts where endpoint destructi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93098</guid>
    </item>
  </channel>
</rss>
