<?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://vulnerability.circl.lu</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>Thu, 01 Oct 2026 20:48:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-45966 — apparmor: fix NULL pointer dereference in __unix_needs_revalidation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-45966</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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://vulnerability.circl.lu/vuln/cve-2026-45966</guid>
    </item>
  </channel>
</rss>
