Vulnerability · Published Feb 22, 2024 · Assigned by Linux

CVE-2023-52443apparmor: avoid crash when parsed profile name is empty

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 15% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 84.8% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

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 "profile :ns::samba-dcerpcd /usr/lib*/samba/{,samba/}samba-dcerpcd {...}" a string ":samba-dcerpcd" is unpacked as a fully-qualified name and then passed to aa_splitn_fqname(). aa_splitn_fqname() treats ":samba-dcerpcd" 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: <TASK> ? 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 </TASK> ---[ 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 is called (e.g. aa_remove_profiles). Well, there is an explicit comment "a ns name without a following profile is allowed" inside. AFAICS, nothing can prevent unpacked "name" to be in form like ":samba-dcerpcd" - it is passed from userspace. Deny the whole profile set replacement in such case and inform user with EPROTO and an explaining message. Found by Linux Verification Center (linuxtesting.org).

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.76-1DEBIAN-CVE-2023-52443
Debian:13linux6.6.15-1DEBIAN-CVE-2023-52443
Debian:14linux6.6.15-1DEBIAN-CVE-2023-52443
Ubuntu:22.04:LTSlinux5.15.0-102.112UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux5.15.0-102.112USN-6725-1
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-aws5.15.0-1057.63UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-aws5.15.0-1057.63USN-6725-2
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-azure5.15.0-1060.69USN-6725-1
Ubuntu:22.04:LTSlinux-azure5.15.0-1060.69UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-azure-6.56.5.0-1022.23~22.04.1USN-6819-1
Ubuntu:22.04:LTSlinux-azure-6.56.5.0-1022.23~22.04.1UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1060.69.1UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1060.69.1USN-6725-1
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-gcp5.15.0-1055.63UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-gcp5.15.0-1055.63USN-6725-1
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-gcp-6.56.5.0-1022.24~22.04.1USN-6818-1
Ubuntu:22.04:LTSlinux-gcp-6.56.5.0-1022.24~22.04.1UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-gke5.15.0-1054.59USN-6725-1
Ubuntu:22.04:LTSlinux-gke5.15.0-1054.59UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1040.46UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1040.46USN-6725-1
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-hwe-6.56.5.0-41.41~22.04.2USN-6818-4
Ubuntu:22.04:LTSlinux-hwe-6.56.5.0-41.41~22.04.2UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-ibm5.15.0-1050.53USN-6725-1
Ubuntu:22.04:LTSlinux-ibm5.15.0-1050.53UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1052.58USN-6725-1
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1052.58UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-kvm5.15.0-1054.59USN-6725-1
Ubuntu:22.04:LTSlinux-kvm5.15.0-1054.59UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-102.112UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-102.112USN-6725-1
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.56.5.0-41.41.1~22.04.1UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.56.5.0-41.41.1~22.04.1USN-6818-1
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1048.48USN-6725-1
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1048.48UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-nvidia-6.56.5.0-1021.22UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-nvidia-6.56.5.0-1021.22USN-6818-3
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1025.25UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1012.12UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-oem-6.16.1.0-1035.35USN-6688-1
Ubuntu:22.04:LTSlinux-oem-6.16.1.0-1035.35UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-oem-6.56.5.0-1024.25UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-oem-6.56.5.0-1024.25USN-6819-3
Ubuntu:22.04:LTSlinux-oracle5.15.0-1055.61USN-6725-1
Ubuntu:22.04:LTSlinux-oracle5.15.0-1055.61UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-oracle-6.56.5.0-1024.24~22.04.1USN-6819-4
Ubuntu:22.04:LTSlinux-oracle-6.56.5.0-1024.24~22.04.1UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-raspi5.15.0-1050.53USN-6725-1
Ubuntu:22.04:LTSlinux-raspi5.15.0-1050.53UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-riscv-6.56.5.0-40.40.1~22.04.1UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-starfive-6.56.5.0-1015.16~22.04.1USN-6819-1
Ubuntu:22.04:LTSlinux-starfive-6.56.5.0-1015.16~22.04.1UBUNTU-CVE-2023-52443
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1030.34UBUNTU-CVE-2023-52443

Affected products (as reported)

VendorProductVersions
Linux Linux 04dc715e24d0820bf8740e1a1135ed61fe162bc8 – before 9286ee97aa4803d99185768735011d0d65827c9e04dc715e24d0820bf8740e1a1135ed61fe162bc8 – before 1d8e62b5569cc1466ceb8a7e4872cf10160a9dcf04dc715e24d0820bf8740e1a1135ed61fe162bc8 – before 5ff00408e5029d3550ee77f62dc15f1e15c47f8704dc715e24d0820bf8740e1a1135ed61fe162bc8 – before 0a12db736edbb4933e4274932aeea594b5876fa404dc715e24d0820bf8740e1a1135ed61fe162bc8 – before 9d4fa5fe2b1d56662afd14915a73b4d0783ffa4504dc715e24d0820bf8740e1a1135ed61fe162bc8 – before 5c0392fdafb0a2321311900be83ffa572bef820304dc715e24d0820bf8740e1a1135ed61fe162bc8 – before 77ab09b92f16c8439a948d1af489196953dc4a0e04dc715e24d0820bf8740e1a1135ed61fe162bc8 – before 55a8210c9e7d21ff2644809699765796d4bfb200
Linux Linux 4.11

References