<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 17:14:48 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-12976</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-12976</link>
      <description>bdu:2025-12976</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-12976</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53445</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-53445</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-53445</guid>
    </item>
    <item>
      <title>EUVD-2026-345210</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345210</link>
      <description>EUVD-2026-345210</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345210</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53445</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-53445</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: qrtr: Fix a refcount bug in qrtr_recvmsg()&lt;/p&gt;
&lt;p&gt;Syzbot reported a bug as following:&lt;/p&gt;
&lt;p&gt;refcount_t: addition on 0; use-after-free.
...
RIP: 0010:refcount_warn_saturate+0x17c/0x1f0 lib/refcount.c:25
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 __refcount_add include/linux/refcount.h:199 [inline]
 __refcount_inc include/linux/refcount.h:250 [inline]
 refcount_inc include/linux/refcount.h:267 [inline]
 kref_get include/linux/kref.h:45 [inline]
 qrtr_node_acquire net/qrtr/af_qrtr.c:202 [inline]
 qrtr_node_lookup net/qrtr/af_qrtr.c:398 [inline]
 qrtr_send_resume_tx net/qrtr/af_qrtr.c:1003 [inline]
 qrtr_recvmsg+0x85f/0x990 net/qrtr/af_qrtr.c:1070
 sock_recvmsg_nosec net/socket.c:1017 [inline]
 sock_recvmsg+0xe2/0x160 net/socket.c:1038
 qrtr_ns_worker+0x170/0x1700 net/qrtr/ns.c:688
 process_one_work+0x991/0x15c0 kernel/workqueue.c:2390
 worker_thread+0x669/0x1090 kernel/workqueue.c:2537&lt;/p&gt;
&lt;p&gt;It occurs in the concurrent scenario of qrtr_recvmsg() and
qrtr_endpoint_unregister() as following:&lt;/p&gt;
&lt;p&gt;cpu0					cpu1
qrtr_recvmsg				qrtr_endpoint_unregister
qrtr_send_resume_tx			qrtr_node_release
qrtr_node_lookup			mutex_lock(&amp;amp;qrtr_node_lock)
spin_lock_irqsave(&amp;amp;qrtr_nodes_lock, )	refcount_dec_and_test(&amp;amp;node-&amp;gt;ref) [node-&amp;gt;ref == 0]
radix_tree_lookup [node != NULL]	__qrtr_node_release
qrtr_node_acquire			spin_lock_irqsave(&amp;amp;qrtr_nodes_lock, )
kref_get(&amp;amp;node-&amp;gt;ref) [WARNING]		...
					mutex_unlock(&amp;amp;qrtr_node_lock)&lt;/p&gt;
&lt;p&gt;Use qrtr_node_lock to protect qrtr_node_l…&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;net: qrtr: Fix a refcount bug in qrtr_recvmsg()&lt;/p&gt;
&lt;p&gt;Syzbot reported a bug as following:&lt;/p&gt;
&lt;p&gt;refcount_t: addition on 0; use-after-free.
...
RIP: 0010:refcount_warn_saturate+0x17c/0x1f0 lib/refcount.c:25
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 __refcount_add include/linux/refcount.h:199 [inline]
 __refcount_inc include/linux/refcount.h:250 [inline]
 refcount_inc include/linux/refcount.h:267 [inline]
 kref_get include/linux/kref.h:45 [inline]
 qrtr_node_acquire net/qrtr/af_qrtr.c:202 [inline]
 qrtr_node_lookup net/qrtr/af_qrtr.c:398 [inline]
 qrtr_send_resume_tx net/qrtr/af_qrtr.c:1003 [inline]
 qrtr_recvmsg+0x85f/0x990 net/qrtr/af_qrtr.c:1070
 sock_recvmsg_nosec net/socket.c:1017 [inline]
 sock_recvmsg+0xe2/0x160 net/socket.c:1038
 qrtr_ns_worker+0x170/0x1700 net/qrtr/ns.c:688
 process_one_work+0x991/0x15c0 kernel/workqueue.c:2390
 worker_thread+0x669/0x1090 kernel/workqueue.c:2537&lt;/p&gt;
&lt;p&gt;It occurs in the concurrent scenario of qrtr_recvmsg() and
qrtr_endpoint_unregister() as following:&lt;/p&gt;
&lt;p&gt;cpu0					cpu1
qrtr_recvmsg				qrtr_endpoint_unregister
qrtr_send_resume_tx			qrtr_node_release
qrtr_node_lookup			mutex_lock(&amp;amp;qrtr_node_lock)
spin_lock_irqsave(&amp;amp;qrtr_nodes_lock, )	refcount_dec_and_test(&amp;amp;node-&amp;gt;ref) [node-&amp;gt;ref == 0]
radix_tree_lookup [node != NULL]	__qrtr_node_release
qrtr_node_acquire			spin_lock_irqsave(&amp;amp;qrtr_nodes_lock, )
kref_get(&amp;amp;node-&amp;gt;ref) [WARNING]		...
					mutex_unlock(&amp;amp;qrtr_node_lock)&lt;/p&gt;
&lt;p&gt;Use qrtr_node_lock to protect qrtr_node_l…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-53445</guid>
    </item>
    <item>
      <title>GHSA-3w47-qc84-prwf</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3w47-qc84-prwf</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: qrtr: Fix a refcount bug in qrtr_recvmsg()&lt;/p&gt;
&lt;p&gt;Syzbot reported a bug as following:&lt;/p&gt;
&lt;p&gt;refcount_t: addition on 0; use-after-free.
...
RIP: 0010:refcount_warn_saturate+0x17c/0x1f0 lib/refcount.c:25
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 __refcount_add include/linux/refcount.h:199 [inline]
 __refcount_inc include/linux/refcount.h:250 [inline]
 refcount_inc include/linux/refcount.h:267 [inline]
 kref_get include/linux/kref.h:45 [inline]
 qrtr_node_acquire net/qrtr/af_qrtr.c:202 [inline]
 qrtr_node_lookup net/qrtr/af_qrtr.c:398 [inline]
 qrtr_send_resume_tx net/qrtr/af_qrtr.c:1003 [inline]
 qrtr_recvmsg+0x85f/0x990 net/qrtr/af_qrtr.c:1070
 sock_recvmsg_nosec net/socket.c:1017 [inline]
 sock_recvmsg+0xe2/0x160 net/socket.c:1038
 qrtr_ns_worker+0x170/0x1700 net/qrtr/ns.c:688
 process_one_work+0x991/0x15c0 kernel/workqueue.c:2390
 worker_thread+0x669/0x1090 kernel/workqueue.c:2537&lt;/p&gt;
&lt;p&gt;It occurs in the concurrent scenario of qrtr_recvmsg() and
qrtr_endpoint_unregister() as following:&lt;/p&gt;
&lt;p&gt;cpu0					cpu1
qrtr_recvmsg				qrtr_endpoint_unregister
qrtr_send_resume_tx			qrtr_node_release
qrtr_node_lookup			mutex_lock(&amp;amp;qrtr_node_lock)
spin_lock_irqsave(&amp;amp;qrtr_nodes_lock, )	refcount_dec_and_test(&amp;amp;node-&amp;gt;ref) [node-&amp;gt;ref == 0]
radix_tree_lookup [node != NULL]	__qrtr_node_release
qrtr_node_acquire			spin_lock_irqsave(&amp;amp;qrtr_nodes_lock, )
kref_get(&amp;amp;node-&amp;gt;ref) [WARNING]		...
					mutex_unlock(&amp;amp;qrtr_node_lock)&lt;/p&gt;
&lt;p&gt;Use qrtr_node_lock to protect qrtr_node_l…&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;net: qrtr: Fix a refcount bug in qrtr_recvmsg()&lt;/p&gt;
&lt;p&gt;Syzbot reported a bug as following:&lt;/p&gt;
&lt;p&gt;refcount_t: addition on 0; use-after-free.
...
RIP: 0010:refcount_warn_saturate+0x17c/0x1f0 lib/refcount.c:25
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 __refcount_add include/linux/refcount.h:199 [inline]
 __refcount_inc include/linux/refcount.h:250 [inline]
 refcount_inc include/linux/refcount.h:267 [inline]
 kref_get include/linux/kref.h:45 [inline]
 qrtr_node_acquire net/qrtr/af_qrtr.c:202 [inline]
 qrtr_node_lookup net/qrtr/af_qrtr.c:398 [inline]
 qrtr_send_resume_tx net/qrtr/af_qrtr.c:1003 [inline]
 qrtr_recvmsg+0x85f/0x990 net/qrtr/af_qrtr.c:1070
 sock_recvmsg_nosec net/socket.c:1017 [inline]
 sock_recvmsg+0xe2/0x160 net/socket.c:1038
 qrtr_ns_worker+0x170/0x1700 net/qrtr/ns.c:688
 process_one_work+0x991/0x15c0 kernel/workqueue.c:2390
 worker_thread+0x669/0x1090 kernel/workqueue.c:2537&lt;/p&gt;
&lt;p&gt;It occurs in the concurrent scenario of qrtr_recvmsg() and
qrtr_endpoint_unregister() as following:&lt;/p&gt;
&lt;p&gt;cpu0					cpu1
qrtr_recvmsg				qrtr_endpoint_unregister
qrtr_send_resume_tx			qrtr_node_release
qrtr_node_lookup			mutex_lock(&amp;amp;qrtr_node_lock)
spin_lock_irqsave(&amp;amp;qrtr_nodes_lock, )	refcount_dec_and_test(&amp;amp;node-&amp;gt;ref) [node-&amp;gt;ref == 0]
radix_tree_lookup [node != NULL]	__qrtr_node_release
qrtr_node_acquire			spin_lock_irqsave(&amp;amp;qrtr_nodes_lock, )
kref_get(&amp;amp;node-&amp;gt;ref) [WARNING]		...
					mutex_unlock(&amp;amp;qrtr_node_lock)&lt;/p&gt;
&lt;p&gt;Use qrtr_node_lock to protect qrtr_node_l…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3w47-qc84-prwf</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53445</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53445</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 109 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: qrtr: Fix a refcount bug in qrtr_recvmsg() Syzbot reported a bug as following: refcount_t: addition on 0; use-after-free. ... RIP: 0010:refcount_warn_saturate+0x17c/0x1f0 lib/refcount.c:25 ... Call Trace:  &amp;lt;TASK&amp;gt;  __refcount_add include/linux/refcount.h:199 [inline]  __refcount_inc include/linux/refcount.h:250 [inline]  refcount_inc include/linux/refcount.h:267 [inline]  kref_get include/linux/kref.h:45 [inline]  qrtr_node_acquire net/qrtr/af_qrtr.c:202 [inline]  qrtr_node_lookup net/qrtr/af_qrtr.c:398 [inline]  qrtr_send_resume_tx net/qrtr/af_qrtr.c:1003 [inline]  qrtr_recvmsg+0x85f/0x990 net/qrtr/af_qrtr.c:1070  sock_recvmsg_nosec net/socket.c:1017 [inline]  sock_recvmsg+0xe2/0x160 net/socket.c:1038  qrtr_ns_worker+0x170/0x1700 net/qrtr/ns.c:688  process_one_work+0x991/0x15c0 kernel/workqueue.c:2390  worker_thread+0x669/0x1090 kernel/workqueue.c:2537 It occurs in the concurrent scenario of qrtr_recvmsg() and qrtr_endpoint_unregister() as following: 	cpu0					cpu1 qrtr_recvmsg				qrtr_endpoint_unregister qrtr_send_resume_tx			qrtr_node_release qrtr_node_lookup			mutex_lock(&amp;amp;qrtr_node_lock) spin_lock_irqsave(&amp;amp;qrtr_nodes_lock, )	refcount_dec_and_test(&amp;amp;node-&amp;gt;ref) [node-&amp;gt;ref == 0] radix_tree_lookup [node != NULL]	__qrtr_node_release qrtr_node_acquire			spin_lock_irqsave(&amp;amp;qrtr_nodes_lock, ) kref_get(&amp;amp;node-&amp;gt;ref) [WARNING]		... 					mutex_unlock(&amp;amp;qrtr_node_lock) Use qrtr_node_lock to protect qrtr_node_lookup(…&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 109 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: qrtr: Fix a refcount bug in qrtr_recvmsg() Syzbot reported a bug as following: refcount_t: addition on 0; use-after-free. ... RIP: 0010:refcount_warn_saturate+0x17c/0x1f0 lib/refcount.c:25 ... Call Trace:  &amp;lt;TASK&amp;gt;  __refcount_add include/linux/refcount.h:199 [inline]  __refcount_inc include/linux/refcount.h:250 [inline]  refcount_inc include/linux/refcount.h:267 [inline]  kref_get include/linux/kref.h:45 [inline]  qrtr_node_acquire net/qrtr/af_qrtr.c:202 [inline]  qrtr_node_lookup net/qrtr/af_qrtr.c:398 [inline]  qrtr_send_resume_tx net/qrtr/af_qrtr.c:1003 [inline]  qrtr_recvmsg+0x85f/0x990 net/qrtr/af_qrtr.c:1070  sock_recvmsg_nosec net/socket.c:1017 [inline]  sock_recvmsg+0xe2/0x160 net/socket.c:1038  qrtr_ns_worker+0x170/0x1700 net/qrtr/ns.c:688  process_one_work+0x991/0x15c0 kernel/workqueue.c:2390  worker_thread+0x669/0x1090 kernel/workqueue.c:2537 It occurs in the concurrent scenario of qrtr_recvmsg() and qrtr_endpoint_unregister() as following: 	cpu0					cpu1 qrtr_recvmsg				qrtr_endpoint_unregister qrtr_send_resume_tx			qrtr_node_release qrtr_node_lookup			mutex_lock(&amp;amp;qrtr_node_lock) spin_lock_irqsave(&amp;amp;qrtr_nodes_lock, )	refcount_dec_and_test(&amp;amp;node-&amp;gt;ref) [node-&amp;gt;ref == 0] radix_tree_lookup [node != NULL]	__qrtr_node_release qrtr_node_acquire			spin_lock_irqsave(&amp;amp;qrtr_nodes_lock, ) kref_get(&amp;amp;node-&amp;gt;ref) [WARNING]		... 					mutex_unlock(&amp;amp;qrtr_node_lock) Use qrtr_node_lock to protect qrtr_node_lookup(…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53445</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2092 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2092</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2092</guid>
    </item>
  </channel>
</rss>
