<?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>Mon, 05 Oct 2026 01:17:09 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-01812</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-01812</link>
      <description>bdu:2024-01812</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-01812</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0363 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de SUSE&lt;/span&gt;. Certaines d'en…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0363</link>
      <description>certfr-2024-avi-0363</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0363</guid>
    </item>
    <item>
      <title>cnvd-2024-30378</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2024-30378</link>
      <description>cnvd-2024-30378</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2024-30378</guid>
    </item>
    <item>
      <title>EUVD-2026-344374</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344374</link>
      <description>EUVD-2026-344374</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344374</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47068</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47068</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/nfc: fix use-after-free llcp_sock_bind/connect&lt;/p&gt;
&lt;p&gt;Commits 8a4cd82d (&amp;#34;nfc: fix refcount leak in llcp_sock_connect()&amp;#34;)
and c33b1cc62 (&amp;#34;nfc: fix refcount leak in llcp_sock_bind()&amp;#34;)
fixed a refcount leak bug in bind/connect but introduced a
use-after-free if the same local is assigned to 2 different sockets.&lt;/p&gt;
&lt;p&gt;This can be triggered by the following simple program:
    int sock1 = socket( AF_NFC, SOCK_STREAM, NFC_SOCKPROTO_LLCP );
    int sock2 = socket( AF_NFC, SOCK_STREAM, NFC_SOCKPROTO_LLCP );
    memset( &amp;amp;addr, 0, sizeof(struct sockaddr_nfc_llcp) );
    addr.sa_family = AF_NFC;
    addr.nfc_protocol = NFC_PROTO_NFC_DEP;
    bind( sock1, (struct sockaddr*) &amp;amp;addr, sizeof(struct sockaddr_nfc_llcp) )
    bind( sock2, (struct sockaddr*) &amp;amp;addr, sizeof(struct sockaddr_nfc_llcp) )
    close(sock1);
    close(sock2);&lt;/p&gt;
&lt;p&gt;Fix this by assigning NULL to llcp_sock-&amp;gt;local after calling
nfc_llcp_local_put.&lt;/p&gt;
&lt;p&gt;This addresses CVE-2021-23134.&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/nfc: fix use-after-free llcp_sock_bind/connect&lt;/p&gt;
&lt;p&gt;Commits 8a4cd82d (&amp;#34;nfc: fix refcount leak in llcp_sock_connect()&amp;#34;)
and c33b1cc62 (&amp;#34;nfc: fix refcount leak in llcp_sock_bind()&amp;#34;)
fixed a refcount leak bug in bind/connect but introduced a
use-after-free if the same local is assigned to 2 different sockets.&lt;/p&gt;
&lt;p&gt;This can be triggered by the following simple program:
    int sock1 = socket( AF_NFC, SOCK_STREAM, NFC_SOCKPROTO_LLCP );
    int sock2 = socket( AF_NFC, SOCK_STREAM, NFC_SOCKPROTO_LLCP );
    memset( &amp;amp;addr, 0, sizeof(struct sockaddr_nfc_llcp) );
    addr.sa_family = AF_NFC;
    addr.nfc_protocol = NFC_PROTO_NFC_DEP;
    bind( sock1, (struct sockaddr*) &amp;amp;addr, sizeof(struct sockaddr_nfc_llcp) )
    bind( sock2, (struct sockaddr*) &amp;amp;addr, sizeof(struct sockaddr_nfc_llcp) )
    close(sock1);
    close(sock2);&lt;/p&gt;
&lt;p&gt;Fix this by assigning NULL to llcp_sock-&amp;gt;local after calling
nfc_llcp_local_put.&lt;/p&gt;
&lt;p&gt;This addresses CVE-2021-23134.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47068</guid>
    </item>
    <item>
      <title>GHSA-47q3-98v3-643r</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-47q3-98v3-643r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/nfc: fix use-after-free llcp_sock_bind/connect&lt;/p&gt;
&lt;p&gt;Commits 8a4cd82d (&amp;#34;nfc: fix refcount leak in llcp_sock_connect()&amp;#34;)
and c33b1cc62 (&amp;#34;nfc: fix refcount leak in llcp_sock_bind()&amp;#34;)
fixed a refcount leak bug in bind/connect but introduced a
use-after-free if the same local is assigned to 2 different sockets.&lt;/p&gt;
&lt;p&gt;This can be triggered by the following simple program:
    int sock1 = socket( AF_NFC, SOCK_STREAM, NFC_SOCKPROTO_LLCP );
    int sock2 = socket( AF_NFC, SOCK_STREAM, NFC_SOCKPROTO_LLCP );
    memset( &amp;amp;addr, 0, sizeof(struct sockaddr_nfc_llcp) );
    addr.sa_family = AF_NFC;
    addr.nfc_protocol = NFC_PROTO_NFC_DEP;
    bind( sock1, (struct sockaddr*) &amp;amp;addr, sizeof(struct sockaddr_nfc_llcp) )
    bind( sock2, (struct sockaddr*) &amp;amp;addr, sizeof(struct sockaddr_nfc_llcp) )
    close(sock1);
    close(sock2);&lt;/p&gt;
&lt;p&gt;Fix this by assigning NULL to llcp_sock-&amp;gt;local after calling
nfc_llcp_local_put.&lt;/p&gt;
&lt;p&gt;This addresses CVE-2021-23134.&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/nfc: fix use-after-free llcp_sock_bind/connect&lt;/p&gt;
&lt;p&gt;Commits 8a4cd82d (&amp;#34;nfc: fix refcount leak in llcp_sock_connect()&amp;#34;)
and c33b1cc62 (&amp;#34;nfc: fix refcount leak in llcp_sock_bind()&amp;#34;)
fixed a refcount leak bug in bind/connect but introduced a
use-after-free if the same local is assigned to 2 different sockets.&lt;/p&gt;
&lt;p&gt;This can be triggered by the following simple program:
    int sock1 = socket( AF_NFC, SOCK_STREAM, NFC_SOCKPROTO_LLCP );
    int sock2 = socket( AF_NFC, SOCK_STREAM, NFC_SOCKPROTO_LLCP );
    memset( &amp;amp;addr, 0, sizeof(struct sockaddr_nfc_llcp) );
    addr.sa_family = AF_NFC;
    addr.nfc_protocol = NFC_PROTO_NFC_DEP;
    bind( sock1, (struct sockaddr*) &amp;amp;addr, sizeof(struct sockaddr_nfc_llcp) )
    bind( sock2, (struct sockaddr*) &amp;amp;addr, sizeof(struct sockaddr_nfc_llcp) )
    close(sock1);
    close(sock2);&lt;/p&gt;
&lt;p&gt;Fix this by assigning NULL to llcp_sock-&amp;gt;local after calling
nfc_llcp_local_put.&lt;/p&gt;
&lt;p&gt;This addresses CVE-2021-23134.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-47q3-98v3-643r</guid>
    </item>
    <item>
      <title>gsd-2021-47068</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-47068</link>
      <description>gsd-2021-47068</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-47068</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1454-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1454-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:1454-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47068</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47068</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/nfc: fix use-after-free llcp_sock_bind/connect Commits 8a4cd82d (&amp;#34;nfc: fix refcount leak in llcp_sock_connect()&amp;#34;) and c33b1cc62 (&amp;#34;nfc: fix refcount leak in llcp_sock_bind()&amp;#34;) fixed a refcount leak bug in bind/connect but introduced a use-after-free if the same local is assigned to 2 different sockets. This can be triggered by the following simple program:     int sock1 = socket( AF_NFC, SOCK_STREAM, NFC_SOCKPROTO_LLCP );     int sock2 = socket( AF_NFC, SOCK_STREAM, NFC_SOCKPROTO_LLCP );     memset( &amp;amp;addr, 0, sizeof(struct sockaddr_nfc_llcp) );     addr.sa_family = AF_NFC;     addr.nfc_protocol = NFC_PROTO_NFC_DEP;     bind( sock1, (struct sockaddr*) &amp;amp;addr, sizeof(struct sockaddr_nfc_llcp) )     bind( sock2, (struct sockaddr*) &amp;amp;addr, sizeof(struct sockaddr_nfc_llcp) )     close(sock1);     close(sock2); Fix this by assigning NULL to llcp_sock-&amp;gt;local after calling nfc_llcp_local_put. This addresses CVE-2021-23134.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/nfc: fix use-after-free llcp_sock_bind/connect Commits 8a4cd82d (&amp;#34;nfc: fix refcount leak in llcp_sock_connect()&amp;#34;) and c33b1cc62 (&amp;#34;nfc: fix refcount leak in llcp_sock_bind()&amp;#34;) fixed a refcount leak bug in bind/connect but introduced a use-after-free if the same local is assigned to 2 different sockets. This can be triggered by the following simple program:     int sock1 = socket( AF_NFC, SOCK_STREAM, NFC_SOCKPROTO_LLCP );     int sock2 = socket( AF_NFC, SOCK_STREAM, NFC_SOCKPROTO_LLCP );     memset( &amp;amp;addr, 0, sizeof(struct sockaddr_nfc_llcp) );     addr.sa_family = AF_NFC;     addr.nfc_protocol = NFC_PROTO_NFC_DEP;     bind( sock1, (struct sockaddr*) &amp;amp;addr, sizeof(struct sockaddr_nfc_llcp) )     bind( sock2, (struct sockaddr*) &amp;amp;addr, sizeof(struct sockaddr_nfc_llcp) )     close(sock1);     close(sock2); Fix this by assigning NULL to llcp_sock-&amp;gt;local after calling nfc_llcp_local_put. This addresses CVE-2021-23134.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47068</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0527 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0527</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand zu verursachen und einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand zu verursachen und einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0527</guid>
    </item>
  </channel>
</rss>
