<?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>Sat, 03 Oct 2026 09:57:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52443 — apparmor: avoid crash when parsed profile name is empty</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2023-52443</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: avoid crash when parsed profile name is empty&lt;/p&gt;
&lt;p&gt;When processing a packed profile in unpack_profile() described like&lt;/p&gt;
&lt;p&gt;&amp;#34;profile :ns::samba-dcerpcd /usr/lib*/samba/{,samba/}samba-dcerpcd {...}&amp;#34;&lt;/p&gt;
&lt;p&gt;a string &amp;#34;:samba-dcerpcd&amp;#34; is unpacked as a fully-qualified name and then
passed to aa_splitn_fqname().&lt;/p&gt;
&lt;p&gt;aa_splitn_fqname() treats &amp;#34;:samba-dcerpcd&amp;#34; as only containing a namespace.
Thus it returns NULL for tmpname, meanwhile tmpns is non-NULL. Later
aa_alloc_profile() crashes as the new profile name is NULL now.&lt;/p&gt;
&lt;p&gt;general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 6 PID: 1657 Comm: apparmor_parser Not tainted 6.7.0-rc2-dirty #16
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-3-gd478f380-rebuilt.opensuse.org 04/01/2014
RIP: 0010:strlen+0x1e/0xa0
Call Trace:
 &amp;lt;TASK&amp;gt;
 ? strlen+0x1e/0xa0
 aa_policy_init+0x1bb/0x230
 aa_alloc_profile+0xb1/0x480
 unpack_profile+0x3bc/0x4960
 aa_unpack+0x309/0x15e0
 aa_replace_profiles+0x213/0x33c0
 policy_update+0x261/0x370
 profile_replace+0x20e/0x2a0
 vfs_write+0x2af/0xe00
 ksys_write+0x126/0x250
 do_syscall_64+0x46/0xf0
 entry_SYSCALL_64_after_hwframe+0x6e/0x76
 &amp;lt;/TASK&amp;gt;
---[ end trace 0000000000000000 ]---
RIP: 0010:strlen+0x1e/0xa0&lt;/p&gt;
&lt;p&gt;It seems such behaviour of aa_splitn_fqname() is expected and checked in
other places wh…&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: avoid crash when parsed profile name is empty&lt;/p&gt;
&lt;p&gt;When processing a packed profile in unpack_profile() described like&lt;/p&gt;
&lt;p&gt;&amp;#34;profile :ns::samba-dcerpcd /usr/lib*/samba/{,samba/}samba-dcerpcd {...}&amp;#34;&lt;/p&gt;
&lt;p&gt;a string &amp;#34;:samba-dcerpcd&amp;#34; is unpacked as a fully-qualified name and then
passed to aa_splitn_fqname().&lt;/p&gt;
&lt;p&gt;aa_splitn_fqname() treats &amp;#34;:samba-dcerpcd&amp;#34; as only containing a namespace.
Thus it returns NULL for tmpname, meanwhile tmpns is non-NULL. Later
aa_alloc_profile() crashes as the new profile name is NULL now.&lt;/p&gt;
&lt;p&gt;general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 6 PID: 1657 Comm: apparmor_parser Not tainted 6.7.0-rc2-dirty #16
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-3-gd478f380-rebuilt.opensuse.org 04/01/2014
RIP: 0010:strlen+0x1e/0xa0
Call Trace:
 &amp;lt;TASK&amp;gt;
 ? strlen+0x1e/0xa0
 aa_policy_init+0x1bb/0x230
 aa_alloc_profile+0xb1/0x480
 unpack_profile+0x3bc/0x4960
 aa_unpack+0x309/0x15e0
 aa_replace_profiles+0x213/0x33c0
 policy_update+0x261/0x370
 profile_replace+0x20e/0x2a0
 vfs_write+0x2af/0xe00
 ksys_write+0x126/0x250
 do_syscall_64+0x46/0xf0
 entry_SYSCALL_64_after_hwframe+0x6e/0x76
 &amp;lt;/TASK&amp;gt;
---[ end trace 0000000000000000 ]---
RIP: 0010:strlen+0x1e/0xa0&lt;/p&gt;
&lt;p&gt;It seems such behaviour of aa_splitn_fqname() is expected and checked in
other places wh…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2023-52443</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-52443</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52443</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:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 152 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: apparmor: avoid crash when parsed profile name is empty When processing a packed profile in unpack_profile() described like  &amp;#34;profile :ns::samba-dcerpcd /usr/lib*/samba/{,samba/}samba-dcerpcd {...}&amp;#34; a string &amp;#34;:samba-dcerpcd&amp;#34; is unpacked as a fully-qualified name and then passed to aa_splitn_fqname(). aa_splitn_fqname() treats &amp;#34;:samba-dcerpcd&amp;#34; as only containing a namespace. Thus it returns NULL for tmpname, meanwhile tmpns is non-NULL. Later aa_alloc_profile() crashes as the new profile name is NULL now. general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 6 PID: 1657 Comm: apparmor_parser Not tainted 6.7.0-rc2-dirty #16 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-3-gd478f380-rebuilt.opensuse.org 04/01/2014 RIP: 0010:strlen+0x1e/0xa0 Call Trace:  &amp;lt;TASK&amp;gt;  ? strlen+0x1e/0xa0  aa_policy_init+0x1bb/0x230  aa_alloc_profile+0xb1/0x480  unpack_profile+0x3bc/0x4960  aa_unpack+0x309/0x15e0  aa_replace_profiles+0x213/0x33c0  policy_update+0x261/0x370  profile_replace+0x20e/0x2a0  vfs_write+0x2af/0xe00  ksys_write+0x126/0x250  do_syscall_64+0x46/0xf0  entry_SYSCALL_64_after_hwframe+0x6e/0x76  &amp;lt;/TASK&amp;gt; ---[ end trace 0000000000000000 ]--- RIP: 0010:strlen+0x1e/0xa0 It seems such behaviour of aa_splitn_fqname() is expected and checked in other places where it…&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:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 152 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: apparmor: avoid crash when parsed profile name is empty When processing a packed profile in unpack_profile() described like  &amp;#34;profile :ns::samba-dcerpcd /usr/lib*/samba/{,samba/}samba-dcerpcd {...}&amp;#34; a string &amp;#34;:samba-dcerpcd&amp;#34; is unpacked as a fully-qualified name and then passed to aa_splitn_fqname(). aa_splitn_fqname() treats &amp;#34;:samba-dcerpcd&amp;#34; as only containing a namespace. Thus it returns NULL for tmpname, meanwhile tmpns is non-NULL. Later aa_alloc_profile() crashes as the new profile name is NULL now. general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 6 PID: 1657 Comm: apparmor_parser Not tainted 6.7.0-rc2-dirty #16 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-3-gd478f380-rebuilt.opensuse.org 04/01/2014 RIP: 0010:strlen+0x1e/0xa0 Call Trace:  &amp;lt;TASK&amp;gt;  ? strlen+0x1e/0xa0  aa_policy_init+0x1bb/0x230  aa_alloc_profile+0xb1/0x480  unpack_profile+0x3bc/0x4960  aa_unpack+0x309/0x15e0  aa_replace_profiles+0x213/0x33c0  policy_update+0x261/0x370  profile_replace+0x20e/0x2a0  vfs_write+0x2af/0xe00  ksys_write+0x126/0x250  do_syscall_64+0x46/0xf0  entry_SYSCALL_64_after_hwframe+0x6e/0x76  &amp;lt;/TASK&amp;gt; ---[ end trace 0000000000000000 ]--- RIP: 0010:strlen+0x1e/0xa0 It seems such behaviour of aa_splitn_fqname() is expected and checked in other places where it…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52443</guid>
    </item>
  </channel>
</rss>
