<?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>Fri, 02 Oct 2026 17:32:20 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-90003</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-90003</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: 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, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-90003</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>EUVD-2026-369514</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-369514</link>
      <description>EUVD-2026-369514</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-369514</guid>
    </item>
    <item>
      <title>fkie_cve-2026-90003</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-90003</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;futex: Prevent rcuwait use-after-free during requeue PI&lt;/p&gt;
&lt;p&gt;On PREEMPT_RT, FUTEX_CMP_REQUEUE_PI can trigger a KASAN report
(slab-out-of-bounds) in futex_requeue_pi_complete() invocation of
rcuwait_wake_up().&lt;/p&gt;
&lt;p&gt;The futex_q used by futex_wait_requeue_pi() is allocated on the waiter&amp;#39;s
stack. An early wakeup can race with a PI requeue as follows:&lt;/p&gt;
&lt;p&gt;waiter                          requeue task
        ------                          ------------
futex_wait_requeue_pi()
  futex_do_wait()
    schedule()
                                       futex_requeue
                                         futex_proxy_trylock_atomic()
                                           futex_requeue_pi_prepare()
                                            Q_REQUEUE_PI_NONE -&amp;gt; Q_REQUEUE_PI_IN_PROGRESS
* timeout/ signal wakes waiter *
  futex_requeue_pi_wakeup_sync()
   Q_REQUEUE_PI_IN_PROGRESS -&amp;gt; Q_REQUEUE_PI_WAIT
                                           requeue_pi_wake_futex
                                             futex_requeue_pi_complete()
                                               cmpxchg Q_REQUEUE_PI_WAIT -&amp;gt; Q_REQUEUE_PI_LOCKED
    rcuwait_wait_event()
      if (atomic_read(&amp;amp;q-&amp;gt;requeue_state) != Q_REQUEUE_PI_WAIT)
       break /* no schedule() */&lt;/p&gt;
&lt;p&gt;/* q.pi_state-&amp;gt;owner == current */
 futex_private_hash_put()
 /* return from syscall */
                                              rcuwait_wake_up(&amp;amp;q-&amp;gt;requeue_wait)…&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;futex: Prevent rcuwait use-after-free during requeue PI&lt;/p&gt;
&lt;p&gt;On PREEMPT_RT, FUTEX_CMP_REQUEUE_PI can trigger a KASAN report
(slab-out-of-bounds) in futex_requeue_pi_complete() invocation of
rcuwait_wake_up().&lt;/p&gt;
&lt;p&gt;The futex_q used by futex_wait_requeue_pi() is allocated on the waiter&amp;#39;s
stack. An early wakeup can race with a PI requeue as follows:&lt;/p&gt;
&lt;p&gt;waiter                          requeue task
        ------                          ------------
futex_wait_requeue_pi()
  futex_do_wait()
    schedule()
                                       futex_requeue
                                         futex_proxy_trylock_atomic()
                                           futex_requeue_pi_prepare()
                                            Q_REQUEUE_PI_NONE -&amp;gt; Q_REQUEUE_PI_IN_PROGRESS
* timeout/ signal wakes waiter *
  futex_requeue_pi_wakeup_sync()
   Q_REQUEUE_PI_IN_PROGRESS -&amp;gt; Q_REQUEUE_PI_WAIT
                                           requeue_pi_wake_futex
                                             futex_requeue_pi_complete()
                                               cmpxchg Q_REQUEUE_PI_WAIT -&amp;gt; Q_REQUEUE_PI_LOCKED
    rcuwait_wait_event()
      if (atomic_read(&amp;amp;q-&amp;gt;requeue_state) != Q_REQUEUE_PI_WAIT)
       break /* no schedule() */&lt;/p&gt;
&lt;p&gt;/* q.pi_state-&amp;gt;owner == current */
 futex_private_hash_put()
 /* return from syscall */
                                              rcuwait_wake_up(&amp;amp;q-&amp;gt;requeue_wait)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-90003</guid>
    </item>
    <item>
      <title>GHSA-m59r-fcc7-pm78</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m59r-fcc7-pm78</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;futex: Prevent rcuwait use-after-free during requeue PI&lt;/p&gt;
&lt;p&gt;On PREEMPT_RT, FUTEX_CMP_REQUEUE_PI can trigger a KASAN report
(slab-out-of-bounds) in futex_requeue_pi_complete() invocation of
rcuwait_wake_up().&lt;/p&gt;
&lt;p&gt;The futex_q used by futex_wait_requeue_pi() is allocated on the waiter&amp;#39;s
stack. An early wakeup can race with a PI requeue as follows:&lt;/p&gt;
&lt;p&gt;waiter                          requeue task
        ------                          ------------
futex_wait_requeue_pi()
  futex_do_wait()
    schedule()
                                       futex_requeue
                                         futex_proxy_trylock_atomic()
                                           futex_requeue_pi_prepare()
                                            Q_REQUEUE_PI_NONE -&amp;gt; Q_REQUEUE_PI_IN_PROGRESS
* timeout/ signal wakes waiter *
  futex_requeue_pi_wakeup_sync()
   Q_REQUEUE_PI_IN_PROGRESS -&amp;gt; Q_REQUEUE_PI_WAIT
                                           requeue_pi_wake_futex
                                             futex_requeue_pi_complete()
                                               cmpxchg Q_REQUEUE_PI_WAIT -&amp;gt; Q_REQUEUE_PI_LOCKED
    rcuwait_wait_event()
      if (atomic_read(&amp;amp;q-&amp;gt;requeue_state) != Q_REQUEUE_PI_WAIT)
       break /* no schedule() */&lt;/p&gt;
&lt;p&gt;/* q.pi_state-&amp;gt;owner == current */
 futex_private_hash_put()
 /* return from syscall */
                                              rcuwait_wake_up(&amp;amp;q-&amp;gt;requeue_wait)…&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;futex: Prevent rcuwait use-after-free during requeue PI&lt;/p&gt;
&lt;p&gt;On PREEMPT_RT, FUTEX_CMP_REQUEUE_PI can trigger a KASAN report
(slab-out-of-bounds) in futex_requeue_pi_complete() invocation of
rcuwait_wake_up().&lt;/p&gt;
&lt;p&gt;The futex_q used by futex_wait_requeue_pi() is allocated on the waiter&amp;#39;s
stack. An early wakeup can race with a PI requeue as follows:&lt;/p&gt;
&lt;p&gt;waiter                          requeue task
        ------                          ------------
futex_wait_requeue_pi()
  futex_do_wait()
    schedule()
                                       futex_requeue
                                         futex_proxy_trylock_atomic()
                                           futex_requeue_pi_prepare()
                                            Q_REQUEUE_PI_NONE -&amp;gt; Q_REQUEUE_PI_IN_PROGRESS
* timeout/ signal wakes waiter *
  futex_requeue_pi_wakeup_sync()
   Q_REQUEUE_PI_IN_PROGRESS -&amp;gt; Q_REQUEUE_PI_WAIT
                                           requeue_pi_wake_futex
                                             futex_requeue_pi_complete()
                                               cmpxchg Q_REQUEUE_PI_WAIT -&amp;gt; Q_REQUEUE_PI_LOCKED
    rcuwait_wait_event()
      if (atomic_read(&amp;amp;q-&amp;gt;requeue_state) != Q_REQUEUE_PI_WAIT)
       break /* no schedule() */&lt;/p&gt;
&lt;p&gt;/* q.pi_state-&amp;gt;owner == current */
 futex_private_hash_put()
 /* return from syscall */
                                              rcuwait_wake_up(&amp;amp;q-&amp;gt;requeue_wait)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m59r-fcc7-pm78</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-90003</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-90003</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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: futex: Prevent rcuwait use-after-free during requeue PI On PREEMPT_RT, FUTEX_CMP_REQUEUE_PI can trigger a KASAN report (slab-out-of-bounds) in futex_requeue_pi_complete() invocation of rcuwait_wake_up(). The futex_q used by futex_wait_requeue_pi() is allocated on the waiter&amp;#39;s stack. An early wakeup can race with a PI requeue as follows:         waiter                          requeue task         ------                          ------------ futex_wait_requeue_pi()   futex_do_wait()     schedule()                                        futex_requeue                                          futex_proxy_trylock_atomic()                                            futex_requeue_pi_prepare()                                             Q_REQUEUE_PI_NONE -&amp;gt; Q_REQUEUE_PI_IN_PROGRESS * timeout/ signal wakes waiter *   futex_requeue_pi_wakeup_sync()    Q_REQUEUE_PI_IN_PROGRESS -&amp;gt; Q_REQUEUE_PI_WAIT                                            requeue_pi_wake_futex                                              futex_requeue_pi_complete()                                                cmpxchg Q_REQUEUE_PI_WAIT -&amp;gt; Q_REQUEUE_PI_LOCKED     rcuwait_wait_event()       if (atomic_read(&amp;amp;q-&amp;gt;requeue_state) != Q_REQUEUE_PI_WAIT)        break /* no schedule() */  /* q.pi_state-&amp;gt;owner == current */  futex_private_hash_put()  /* return from syscall */ rcuwait_wake_up(&amp;amp;q-&amp;gt;requeue_wait)                                                 /* q…&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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: futex: Prevent rcuwait use-after-free during requeue PI On PREEMPT_RT, FUTEX_CMP_REQUEUE_PI can trigger a KASAN report (slab-out-of-bounds) in futex_requeue_pi_complete() invocation of rcuwait_wake_up(). The futex_q used by futex_wait_requeue_pi() is allocated on the waiter&amp;#39;s stack. An early wakeup can race with a PI requeue as follows:         waiter                          requeue task         ------                          ------------ futex_wait_requeue_pi()   futex_do_wait()     schedule()                                        futex_requeue                                          futex_proxy_trylock_atomic()                                            futex_requeue_pi_prepare()                                             Q_REQUEUE_PI_NONE -&amp;gt; Q_REQUEUE_PI_IN_PROGRESS * timeout/ signal wakes waiter *   futex_requeue_pi_wakeup_sync()    Q_REQUEUE_PI_IN_PROGRESS -&amp;gt; Q_REQUEUE_PI_WAIT                                            requeue_pi_wake_futex                                              futex_requeue_pi_complete()                                                cmpxchg Q_REQUEUE_PI_WAIT -&amp;gt; Q_REQUEUE_PI_LOCKED     rcuwait_wait_event()       if (atomic_read(&amp;amp;q-&amp;gt;requeue_state) != Q_REQUEUE_PI_WAIT)        break /* no schedule() */  /* q.pi_state-&amp;gt;owner == current */  futex_private_hash_put()  /* return from syscall */ rcuwait_wake_up(&amp;amp;q-&amp;gt;requeue_wait)                                                 /* q…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-90003</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3438 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3438</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service zu verursachen oder eine nicht näher spezifizierte Auswirkung zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service zu verursachen oder eine nicht näher spezifizierte Auswirkung zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3438</guid>
    </item>
  </channel>
</rss>
