<?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>Sun, 04 Oct 2026 06:14:04 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80666</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-80666</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-2026-80666</guid>
    </item>
    <item>
      <title>EUVD-2026-361044</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-361044</link>
      <description>EUVD-2026-361044</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-361044</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80666</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80666</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: sco: Fix a race condition in sco_sock_timeout()&lt;/p&gt;
&lt;p&gt;sco_sock_timeout() runs asynchronously and lock_sock(sk). If the socket
is closing while the timer is running, it holds the same lock
(lock_sock(sk)) twice, leading to a deadlock.&lt;/p&gt;
&lt;p&gt;CPU 0                      CPU 1
====================       ======================
sco_sock_close()
                           sco_sock_timeout()
lock_sock(sk) // &amp;lt;-- LOCK
  __sco_sock_close()
    sco_chan_del()
      sco_conn_put()
	      sco_conn_free()
	        disable_delayed_work_sync()
	                           lock(sk) // &amp;lt;-- SAME LOCK&lt;/p&gt;
&lt;p&gt;Fix this by moving disable_delayed_work_sync() outside of lock_sock(sk),
ensuring that no lock_sock(sk) is held before sco_sock_timeout().&lt;/p&gt;
&lt;p&gt;Lockdep splat:&lt;/p&gt;
&lt;p&gt;WARNING: possible circular locking dependency detected
6.13.0-rc4 #7 Not tainted&lt;/p&gt;
&lt;p&gt;syz-executor292/9514 is trying to acquire lock:
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: rcu_lock_acquire sect/v6.13-rc4/./include/linux/rcupdate.h:337 [inline]
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: rcu_read_lock sect/v6.13-rc4/./include/linux/rcupdate.h:849 [inline]
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: start_flush_work sect/v6.13-rc4/kernel/workqueue.c:4137 [inline]
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: __flush_work+…&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;Bluetooth: sco: Fix a race condition in sco_sock_timeout()&lt;/p&gt;
&lt;p&gt;sco_sock_timeout() runs asynchronously and lock_sock(sk). If the socket
is closing while the timer is running, it holds the same lock
(lock_sock(sk)) twice, leading to a deadlock.&lt;/p&gt;
&lt;p&gt;CPU 0                      CPU 1
====================       ======================
sco_sock_close()
                           sco_sock_timeout()
lock_sock(sk) // &amp;lt;-- LOCK
  __sco_sock_close()
    sco_chan_del()
      sco_conn_put()
	      sco_conn_free()
	        disable_delayed_work_sync()
	                           lock(sk) // &amp;lt;-- SAME LOCK&lt;/p&gt;
&lt;p&gt;Fix this by moving disable_delayed_work_sync() outside of lock_sock(sk),
ensuring that no lock_sock(sk) is held before sco_sock_timeout().&lt;/p&gt;
&lt;p&gt;Lockdep splat:&lt;/p&gt;
&lt;p&gt;WARNING: possible circular locking dependency detected
6.13.0-rc4 #7 Not tainted&lt;/p&gt;
&lt;p&gt;syz-executor292/9514 is trying to acquire lock:
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: rcu_lock_acquire sect/v6.13-rc4/./include/linux/rcupdate.h:337 [inline]
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: rcu_read_lock sect/v6.13-rc4/./include/linux/rcupdate.h:849 [inline]
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: start_flush_work sect/v6.13-rc4/kernel/workqueue.c:4137 [inline]
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: __flush_work+…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-80666</guid>
    </item>
    <item>
      <title>GHSA-53mq-p582-hhfx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-53mq-p582-hhfx</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: sco: Fix a race condition in sco_sock_timeout()&lt;/p&gt;
&lt;p&gt;sco_sock_timeout() runs asynchronously and lock_sock(sk). If the socket
is closing while the timer is running, it holds the same lock
(lock_sock(sk)) twice, leading to a deadlock.&lt;/p&gt;
&lt;p&gt;CPU 0                      CPU 1
====================       ======================
sco_sock_close()
                           sco_sock_timeout()
lock_sock(sk) // &amp;lt;-- LOCK
  __sco_sock_close()
    sco_chan_del()
      sco_conn_put()
	      sco_conn_free()
	        disable_delayed_work_sync()
	                           lock(sk) // &amp;lt;-- SAME LOCK&lt;/p&gt;
&lt;p&gt;Fix this by moving disable_delayed_work_sync() outside of lock_sock(sk),
ensuring that no lock_sock(sk) is held before sco_sock_timeout().&lt;/p&gt;
&lt;p&gt;Lockdep splat:&lt;/p&gt;
&lt;p&gt;WARNING: possible circular locking dependency detected
6.13.0-rc4 #7 Not tainted&lt;/p&gt;
&lt;p&gt;syz-executor292/9514 is trying to acquire lock:
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: rcu_lock_acquire sect/v6.13-rc4/./include/linux/rcupdate.h:337 [inline]
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: rcu_read_lock sect/v6.13-rc4/./include/linux/rcupdate.h:849 [inline]
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: start_flush_work sect/v6.13-rc4/kernel/workqueue.c:4137 [inline]
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: __flush_work+…&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;Bluetooth: sco: Fix a race condition in sco_sock_timeout()&lt;/p&gt;
&lt;p&gt;sco_sock_timeout() runs asynchronously and lock_sock(sk). If the socket
is closing while the timer is running, it holds the same lock
(lock_sock(sk)) twice, leading to a deadlock.&lt;/p&gt;
&lt;p&gt;CPU 0                      CPU 1
====================       ======================
sco_sock_close()
                           sco_sock_timeout()
lock_sock(sk) // &amp;lt;-- LOCK
  __sco_sock_close()
    sco_chan_del()
      sco_conn_put()
	      sco_conn_free()
	        disable_delayed_work_sync()
	                           lock(sk) // &amp;lt;-- SAME LOCK&lt;/p&gt;
&lt;p&gt;Fix this by moving disable_delayed_work_sync() outside of lock_sock(sk),
ensuring that no lock_sock(sk) is held before sco_sock_timeout().&lt;/p&gt;
&lt;p&gt;Lockdep splat:&lt;/p&gt;
&lt;p&gt;WARNING: possible circular locking dependency detected
6.13.0-rc4 #7 Not tainted&lt;/p&gt;
&lt;p&gt;syz-executor292/9514 is trying to acquire lock:
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: rcu_lock_acquire sect/v6.13-rc4/./include/linux/rcupdate.h:337 [inline]
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: rcu_read_lock sect/v6.13-rc4/./include/linux/rcupdate.h:849 [inline]
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: start_flush_work sect/v6.13-rc4/kernel/workqueue.c:4137 [inline]
ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: __flush_work+…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-53mq-p582-hhfx</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80666</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80666</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: sco: Fix a race condition in sco_sock_timeout() sco_sock_timeout() runs asynchronously and lock_sock(sk). If the socket is closing while the timer is running, it holds the same lock (lock_sock(sk)) twice, leading to a deadlock. CPU 0                      CPU 1 ====================       ====================== sco_sock_close()                            sco_sock_timeout() lock_sock(sk) // &amp;lt;-- LOCK   __sco_sock_close()     sco_chan_del()       sco_conn_put() 	      sco_conn_free() 	        disable_delayed_work_sync() 	                           lock(sk) // &amp;lt;-- SAME LOCK Fix this by moving disable_delayed_work_sync() outside of lock_sock(sk), ensuring that no lock_sock(sk) is held before sco_sock_timeout(). Lockdep splat: WARNING: possible circular locking dependency detected 6.13.0-rc4 #7 Not tainted syz-executor292/9514 is trying to acquire lock: ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: rcu_lock_acquire sect/v6.13-rc4/./include/linux/rcupdate.h:337 [inline] ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: rcu_read_lock sect/v6.13-rc4/./include/linux/rcupdate.h:849 [inline] ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: start_flush_work sect/v6.13-rc4/kernel/workqueue.c:4137 [inline] ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: __flush_work+0xd1/0x…&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: sco: Fix a race condition in sco_sock_timeout() sco_sock_timeout() runs asynchronously and lock_sock(sk). If the socket is closing while the timer is running, it holds the same lock (lock_sock(sk)) twice, leading to a deadlock. CPU 0                      CPU 1 ====================       ====================== sco_sock_close()                            sco_sock_timeout() lock_sock(sk) // &amp;lt;-- LOCK   __sco_sock_close()     sco_chan_del()       sco_conn_put() 	      sco_conn_free() 	        disable_delayed_work_sync() 	                           lock(sk) // &amp;lt;-- SAME LOCK Fix this by moving disable_delayed_work_sync() outside of lock_sock(sk), ensuring that no lock_sock(sk) is held before sco_sock_timeout(). Lockdep splat: WARNING: possible circular locking dependency detected 6.13.0-rc4 #7 Not tainted syz-executor292/9514 is trying to acquire lock: ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: rcu_lock_acquire sect/v6.13-rc4/./include/linux/rcupdate.h:337 [inline] ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: rcu_read_lock sect/v6.13-rc4/./include/linux/rcupdate.h:849 [inline] ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: start_flush_work sect/v6.13-rc4/kernel/workqueue.c:4137 [inline] ffff8881115d5070 ((work_completion)(&amp;amp;(&amp;amp;conn-&amp;gt;timeout_work)-&amp;gt;work)){+.+.}-{0:0}, at: __flush_work+0xd1/0x…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80666</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3075 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</guid>
    </item>
  </channel>
</rss>
