<?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 23:32:01 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-13815</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-13815</link>
      <description>bdu:2026-13815</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-13815</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-45966</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-45966</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-45966</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0695 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0695</link>
      <description>certfr-2026-avi-0695</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0695</guid>
    </item>
    <item>
      <title>EUVD-2026-321864</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-321864</link>
      <description>EUVD-2026-321864</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-321864</guid>
    </item>
    <item>
      <title>fkie_cve-2026-45966</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-45966</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;apparmor: fix NULL pointer dereference in __unix_needs_revalidation&lt;/p&gt;
&lt;p&gt;When receiving file descriptors via SCM_RIGHTS, both the socket pointer
and the socket&amp;#39;s sk pointer can be NULL during socket setup or teardown,
causing NULL pointer dereferences in __unix_needs_revalidation().&lt;/p&gt;
&lt;p&gt;This is a regression in AppArmor 5.0.0 (kernel 6.17+) where the new
__unix_needs_revalidation() function was added without proper NULL checks.&lt;/p&gt;
&lt;p&gt;The crash manifests as:
  BUG: kernel NULL pointer dereference, address: 0x0000000000000018
  RIP: aa_file_perm+0xb7/0x3b0 (or +0xbe/0x3b0, +0xc0/0x3e0)
  Call Trace:
   apparmor_file_receive+0x42/0x80
   security_file_receive+0x2e/0x50
   receive_fd+0x1d/0xf0
   scm_detach_fds+0xad/0x1c0&lt;/p&gt;
&lt;p&gt;The function dereferences sock-&amp;gt;sk-&amp;gt;sk_family without checking if either
sock or sock-&amp;gt;sk is NULL first.&lt;/p&gt;
&lt;p&gt;Add NULL checks for both sock and sock-&amp;gt;sk before accessing sk_family.&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;apparmor: fix NULL pointer dereference in __unix_needs_revalidation&lt;/p&gt;
&lt;p&gt;When receiving file descriptors via SCM_RIGHTS, both the socket pointer
and the socket&amp;#39;s sk pointer can be NULL during socket setup or teardown,
causing NULL pointer dereferences in __unix_needs_revalidation().&lt;/p&gt;
&lt;p&gt;This is a regression in AppArmor 5.0.0 (kernel 6.17+) where the new
__unix_needs_revalidation() function was added without proper NULL checks.&lt;/p&gt;
&lt;p&gt;The crash manifests as:
  BUG: kernel NULL pointer dereference, address: 0x0000000000000018
  RIP: aa_file_perm+0xb7/0x3b0 (or +0xbe/0x3b0, +0xc0/0x3e0)
  Call Trace:
   apparmor_file_receive+0x42/0x80
   security_file_receive+0x2e/0x50
   receive_fd+0x1d/0xf0
   scm_detach_fds+0xad/0x1c0&lt;/p&gt;
&lt;p&gt;The function dereferences sock-&amp;gt;sk-&amp;gt;sk_family without checking if either
sock or sock-&amp;gt;sk is NULL first.&lt;/p&gt;
&lt;p&gt;Add NULL checks for both sock and sock-&amp;gt;sk before accessing sk_family.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-45966</guid>
    </item>
    <item>
      <title>GHSA-g4q8-m3pw-qhvv</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g4q8-m3pw-qhvv</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;apparmor: fix NULL pointer dereference in __unix_needs_revalidation&lt;/p&gt;
&lt;p&gt;When receiving file descriptors via SCM_RIGHTS, both the socket pointer
and the socket&amp;#39;s sk pointer can be NULL during socket setup or teardown,
causing NULL pointer dereferences in __unix_needs_revalidation().&lt;/p&gt;
&lt;p&gt;This is a regression in AppArmor 5.0.0 (kernel 6.17+) where the new
__unix_needs_revalidation() function was added without proper NULL checks.&lt;/p&gt;
&lt;p&gt;The crash manifests as:
  BUG: kernel NULL pointer dereference, address: 0x0000000000000018
  RIP: aa_file_perm+0xb7/0x3b0 (or +0xbe/0x3b0, +0xc0/0x3e0)
  Call Trace:
   apparmor_file_receive+0x42/0x80
   security_file_receive+0x2e/0x50
   receive_fd+0x1d/0xf0
   scm_detach_fds+0xad/0x1c0&lt;/p&gt;
&lt;p&gt;The function dereferences sock-&amp;gt;sk-&amp;gt;sk_family without checking if either
sock or sock-&amp;gt;sk is NULL first.&lt;/p&gt;
&lt;p&gt;Add NULL checks for both sock and sock-&amp;gt;sk before accessing sk_family.&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;apparmor: fix NULL pointer dereference in __unix_needs_revalidation&lt;/p&gt;
&lt;p&gt;When receiving file descriptors via SCM_RIGHTS, both the socket pointer
and the socket&amp;#39;s sk pointer can be NULL during socket setup or teardown,
causing NULL pointer dereferences in __unix_needs_revalidation().&lt;/p&gt;
&lt;p&gt;This is a regression in AppArmor 5.0.0 (kernel 6.17+) where the new
__unix_needs_revalidation() function was added without proper NULL checks.&lt;/p&gt;
&lt;p&gt;The crash manifests as:
  BUG: kernel NULL pointer dereference, address: 0x0000000000000018
  RIP: aa_file_perm+0xb7/0x3b0 (or +0xbe/0x3b0, +0xc0/0x3e0)
  Call Trace:
   apparmor_file_receive+0x42/0x80
   security_file_receive+0x2e/0x50
   receive_fd+0x1d/0xf0
   scm_detach_fds+0xad/0x1c0&lt;/p&gt;
&lt;p&gt;The function dereferences sock-&amp;gt;sk-&amp;gt;sk_family without checking if either
sock or sock-&amp;gt;sk is NULL first.&lt;/p&gt;
&lt;p&gt;Add NULL checks for both sock and sock-&amp;gt;sk before accessing sk_family.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g4q8-m3pw-qhvv</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-45966</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-45966</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 103 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: apparmor: fix NULL pointer dereference in __unix_needs_revalidation When receiving file descriptors via SCM_RIGHTS, both the socket pointer and the socket&amp;#39;s sk pointer can be NULL during socket setup or teardown, causing NULL pointer dereferences in __unix_needs_revalidation(). This is a regression in AppArmor 5.0.0 (kernel 6.17+) where the new __unix_needs_revalidation() function was added without proper NULL checks. The crash manifests as:   BUG: kernel NULL pointer dereference, address: 0x0000000000000018   RIP: aa_file_perm+0xb7/0x3b0 (or +0xbe/0x3b0, +0xc0/0x3e0)   Call Trace:    apparmor_file_receive+0x42/0x80    security_file_receive+0x2e/0x50    receive_fd+0x1d/0xf0    scm_detach_fds+0xad/0x1c0 The function dereferences sock-&amp;gt;sk-&amp;gt;sk_family without checking if either sock or sock-&amp;gt;sk is NULL first. Add NULL checks for both sock and sock-&amp;gt;sk before accessing sk_family.&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 103 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: apparmor: fix NULL pointer dereference in __unix_needs_revalidation When receiving file descriptors via SCM_RIGHTS, both the socket pointer and the socket&amp;#39;s sk pointer can be NULL during socket setup or teardown, causing NULL pointer dereferences in __unix_needs_revalidation(). This is a regression in AppArmor 5.0.0 (kernel 6.17+) where the new __unix_needs_revalidation() function was added without proper NULL checks. The crash manifests as:   BUG: kernel NULL pointer dereference, address: 0x0000000000000018   RIP: aa_file_perm+0xb7/0x3b0 (or +0xbe/0x3b0, +0xc0/0x3e0)   Call Trace:    apparmor_file_receive+0x42/0x80    security_file_receive+0x2e/0x50    receive_fd+0x1d/0xf0    scm_detach_fds+0xad/0x1c0 The function dereferences sock-&amp;gt;sk-&amp;gt;sk_family without checking if either sock or sock-&amp;gt;sk is NULL first. Add NULL checks for both sock and sock-&amp;gt;sk before accessing sk_family.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-45966</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1700 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700</guid>
    </item>
  </channel>
</rss>
