<?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-10-04T17:06:29.175400+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/bdu:2026-11591</id>
    <title>bdu:2026-11591</title>
    <updated>2026-10-04T17:06:29.445036+00:00</updated>
    <content>bdu:2026-11591</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-11591"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-23150</id>
    <title>BELL-CVE-2026-23150</title>
    <updated>2026-10-04T17:06:29.445096+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-23150"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316</id>
    <title>certfr-2026-avi-0316 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
    <updated>2026-10-04T17:06:29.445130+00:00</updated>
    <content>certfr-2026-avi-0316</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-315371</id>
    <title>EUVD-2026-315371</title>
    <updated>2026-10-04T17:06:29.445149+00:00</updated>
    <content>EUVD-2026-315371</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-315371"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23150</id>
    <title>fkie_cve-2026-23150</title>
    <updated>2026-10-04T17:06:29.445160+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>nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame().</p>
<p>syzbot reported various memory leaks related to NFC, struct
nfc_llcp_sock, sk_buff, nfc_dev, etc. [0]</p>
<p>The leading log hinted that nfc_llcp_send_ui_frame() failed
to allocate skb due to sock_error(sk) being -ENXIO.</p>
<p>ENXIO is set by nfc_llcp_socket_release() when struct
nfc_llcp_local is destroyed by local_cleanup().</p>
<p>The problem is that there is no synchronisation between
nfc_llcp_send_ui_frame() and local_cleanup(), and skb
could be put into local-&gt;tx_queue after it was purged in
local_cleanup():</p>
<p>CPU1                          CPU2
  ----                          ----
  nfc_llcp_send_ui_frame()      local_cleanup()
  |- do {                       '
     |- pdu = nfc_alloc_send_skb(..., &amp;err)
     |                          .
     |                          |- nfc_llcp_socket_release(local, false, ENXIO);
     |                          |- skb_queue_purge(&amp;local-&gt;tx_queue);      |
     |                          '                                          |
     |- skb_queue_tail(&amp;local-&gt;tx_queue, pdu);                             |
    ...                                                                    |
     |- pdu = nfc_alloc_send_skb(..., &amp;err)                                |
                                       ^._________________________________.'</p>
<p>local_cleanup() is called for struct nfc_llcp_local only
after nfc_llcp_remove_local() unlinks…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-23150"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-2j2f-9hjh-v2xm</id>
    <title>GHSA-2j2f-9hjh-v2xm</title>
    <updated>2026-10-04T17:06:29.445215+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>nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame().</p>
<p>syzbot reported various memory leaks related to NFC, struct
nfc_llcp_sock, sk_buff, nfc_dev, etc. [0]</p>
<p>The leading log hinted that nfc_llcp_send_ui_frame() failed
to allocate skb due to sock_error(sk) being -ENXIO.</p>
<p>ENXIO is set by nfc_llcp_socket_release() when struct
nfc_llcp_local is destroyed by local_cleanup().</p>
<p>The problem is that there is no synchronisation between
nfc_llcp_send_ui_frame() and local_cleanup(), and skb
could be put into local-&gt;tx_queue after it was purged in
local_cleanup():</p>
<p>CPU1                          CPU2
  ----                          ----
  nfc_llcp_send_ui_frame()      local_cleanup()
  |- do {                       '
     |- pdu = nfc_alloc_send_skb(..., &amp;err)
     |                          .
     |                          |- nfc_llcp_socket_release(local, false, ENXIO);
     |                          |- skb_queue_purge(&amp;local-&gt;tx_queue);      |
     |                          '                                          |
     |- skb_queue_tail(&amp;local-&gt;tx_queue, pdu);                             |
    ...                                                                    |
     |- pdu = nfc_alloc_send_skb(..., &amp;err)                                |
                                       ^._________________________________.'</p>
<p>local_cleanup() is called for struct nfc_llcp_local only
after nfc_llcp_remove_local() unlinks…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-2j2f-9hjh-v2xm"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20416-1</id>
    <title>openSUSE-SU-2026:20416-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-04T17:06:29.445257+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for the Linux Kernel</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2026:20416-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2026:0962-1</id>
    <title>SUSE-SU-2026:0962-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-04T17:06:29.445371+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for the Linux Kernel</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2026:0962-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23150</id>
    <title>UBUNTU-CVE-2026-23150</title>
    <updated>2026-10-04T17:06:29.445471+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 231 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame(). syzbot reported various memory leaks related to NFC, struct nfc_llcp_sock, sk_buff, nfc_dev, etc. [0] The leading log hinted that nfc_llcp_send_ui_frame() failed to allocate skb due to sock_error(sk) being -ENXIO. ENXIO is set by nfc_llcp_socket_release() when struct nfc_llcp_local is destroyed by local_cleanup(). The problem is that there is no synchronisation between nfc_llcp_send_ui_frame() and local_cleanup(), and skb could be put into local-&gt;tx_queue after it was purged in local_cleanup():   CPU1                          CPU2   ----                          ----   nfc_llcp_send_ui_frame()      local_cleanup()   |- do {                       '      |- pdu = nfc_alloc_send_skb(..., &amp;err)      |                          .      |                          |- nfc_llcp_socket_release(local, false, ENXIO);      |                          |- skb_queue_purge(&amp;local-&gt;tx_queue); |      |                          ' |      |- skb_queue_tail(&amp;local-&gt;tx_queue, pdu); |     ... |      |- pdu = nfc_alloc_send_skb(..., &amp;err) | ^._________________________________.' local_cleanup() is called for struct nfc_llcp_local only after nfc_llcp_remove_local() unlinks it from llcp_devices. If we hold local-&gt;tx_queue.lock then, we can synchronise the thread and nfc_llcp_send_ui_frame(). Let's do that and check list_empty(&amp;local-&gt;list) before queuing skb to local-&gt;tx_queue in nfc_llcp…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23150"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0421</id>
    <title>WID-SEC-W-2026-0421 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-04T17:06:29.445781+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 nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0421"/>
  </entry>
</feed>
