<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-20T18:58:28.905196+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-99231</id>
    <title>BELL-CVE-2026-99231</title>
    <updated>2026-11-20T18:58:28.916584+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:25: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-99231"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1596</id>
    <title>certfr-2026-avi-1596 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
    <updated>2026-11-20T18:58:28.916637+00:00</updated>
    <content>certfr-2026-avi-1596</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1596"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-399112</id>
    <title>EUVD-2026-399112</title>
    <updated>2026-11-20T18:58:28.916657+00:00</updated>
    <content>EUVD-2026-399112</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-399112"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99231</id>
    <title>fkie_cve-2026-99231</title>
    <updated>2026-11-20T18:58:28.916671+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>io_uring/waitid: own the request before clearing -&gt;head</p>
<p>io_waitid_remove_wq() only takes the wait queue lock if -&gt;head is set.
io_waitid_wait() clears -&gt;head first thing, before it tries to become the
owner of the request by bumping -&gt;refs. If somebody else owns the request
at that point, nothing keeps it from completing the request while the
wake up handler is still going to touch it:</p>
<p>CPU0 (io_waitid_wait)                 CPU1 (io_waitid, holds a ref)
list_del_init(&amp;wait-&gt;entry)
smp_store_release(&amp;iw-&gt;head, NULL)
                                      __do_wait() finds another child
                                      io_waitid_remove_wq()
                                        // -&gt;head == NULL, no locking
                                      io_waitid_finish(), IOU_COMPLETE
                                      // request freed and reused
atomic_fetch_inc(&amp;iw-&gt;refs)</p>
<p>The same goes for __io_waitid_cancel() if it claims the request in that
window. -&gt;refs is part of the per opcode data of the request, so this
increments whatever the next user of the request keeps there. If that
happens to be zero, the handler concludes that it owns the request, and
queues io_waitid_cb() for it. With the window held open by a delay, and
the request reused for a receive that is waiting for data:</p>
<p>BUG: KASAN: slab-use-after-free in __wake_up_common+0x1ca/0x1f0
   __wake_up_sync_key+0x36/0x50
   sock_def_readable+0xf1/0x…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-99231"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-r5jr-3m3c-4rp2</id>
    <title>GHSA-r5jr-3m3c-4rp2</title>
    <updated>2026-11-20T18:58:28.916719+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>io_uring/waitid: own the request before clearing -&gt;head</p>
<p>io_waitid_remove_wq() only takes the wait queue lock if -&gt;head is set.
io_waitid_wait() clears -&gt;head first thing, before it tries to become the
owner of the request by bumping -&gt;refs. If somebody else owns the request
at that point, nothing keeps it from completing the request while the
wake up handler is still going to touch it:</p>
<p>CPU0 (io_waitid_wait)                 CPU1 (io_waitid, holds a ref)
list_del_init(&amp;wait-&gt;entry)
smp_store_release(&amp;iw-&gt;head, NULL)
                                      __do_wait() finds another child
                                      io_waitid_remove_wq()
                                        // -&gt;head == NULL, no locking
                                      io_waitid_finish(), IOU_COMPLETE
                                      // request freed and reused
atomic_fetch_inc(&amp;iw-&gt;refs)</p>
<p>The same goes for __io_waitid_cancel() if it claims the request in that
window. -&gt;refs is part of the per opcode data of the request, so this
increments whatever the next user of the request keeps there. If that
happens to be zero, the handler concludes that it owns the request, and
queues io_waitid_cb() for it. With the window held open by a delay, and
the request reused for a receive that is waiting for data:</p>
<p>BUG: KASAN: slab-use-after-free in __wake_up_common+0x1ca/0x1f0
   __wake_up_sync_key+0x36/0x50
   sock_def_readable+0xf1/0x…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-r5jr-3m3c-4rp2"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99231</id>
    <title>msrc_CVE-2026-99231 — io_uring/waitid: own the request before clearing -&gt;head</title>
    <updated>2026-11-20T18:58:28.916766+00:00</updated>
    <content>msrc_CVE-2026-99231</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-99231"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99231</id>
    <title>UBUNTU-CVE-2026-99231</title>
    <updated>2026-11-20T18:58:28.916811+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 160 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: own the request before clearing -&gt;head io_waitid_remove_wq() only takes the wait queue lock if -&gt;head is set. io_waitid_wait() clears -&gt;head first thing, before it tries to become the owner of the request by bumping -&gt;refs. If somebody else owns the request at that point, nothing keeps it from completing the request while the wake up handler is still going to touch it: CPU0 (io_waitid_wait)                 CPU1 (io_waitid, holds a ref) list_del_init(&amp;wait-&gt;entry) smp_store_release(&amp;iw-&gt;head, NULL)                                       __do_wait() finds another child                                       io_waitid_remove_wq()                                         // -&gt;head == NULL, no locking                                       io_waitid_finish(), IOU_COMPLETE                                       // request freed and reused atomic_fetch_inc(&amp;iw-&gt;refs) The same goes for __io_waitid_cancel() if it claims the request in that window. -&gt;refs is part of the per opcode data of the request, so this increments whatever the next user of the request keeps there. If that happens to be zero, the handler concludes that it owns the request, and queues io_waitid_cb() for it. With the window held open by a delay, and the request reused for a receive that is waiting for data:   BUG: KASAN: slab-use-after-free in __wake_up_common+0x1ca/0x1f0    __wake_up_sync_key+0x36/0x50    sock_def_readable+0xf1/0x420…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99231"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4302</id>
    <title>WID-SEC-W-2026-4302 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
    <updated>2026-11-20T18:58:28.917036+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Auslösung eines Denial-of-Service-Angriffs, die Manipulation oder Offenlegung von Daten, die Ausführung von beliebigem Code, die Erlangung erweiterter Berechtigungen oder die Umgehung von Sicherheitsmaßnahmen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4302"/>
  </entry>
</feed>
