LiveActive security incident?Get immediate response
CVE Record

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

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).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-52443 is a Linux kernel AppArmor bug where a malformed profile name can trigger a kernel crash during profile replacement. The business impact is denial of service on systems using AppArmor, not data theft. Sources do not show active exploitation or a CVSS score.

Executive priority

Prioritize normal kernel patching for AppArmor-enabled servers, especially multi-user or managed-hosting environments. Escalate only if internal systems allow less-trusted users or automation to submit AppArmor profiles.

Technical view

AppArmor unpack_profile() can pass an empty parsed profile name to aa_alloc_profile() after aa_splitn_fqname() treats a string like ':name' as namespace-only. This causes a NULL pointer dereference in strlen() during profile replacement. The fix rejects the profile set replacement with EPROTO instead of crashing.

Likely exposure

Most relevant to Linux systems with AppArmor enabled and vulnerable or unpatched kernel builds. Practical exposure appears limited to actors or processes able to load or replace AppArmor profiles, which is usually privileged administrative activity.

Exploitation context

The source describes a crash reachable from userspace through AppArmor profile parsing, but gives no evidence of in-the-wild exploitation. It is not listed as CISA KEV in the provided bundle. Treat it as a local denial-of-service risk unless vendor guidance says otherwise.

Researcher notes

Evidence supports a kernel crash during profile replacement, not privilege escalation or remote code execution. The affected-version data is incomplete in the bundle, so rely on distribution kernel advisories and stable commit backports for exact exposure mapping.

Mitigation direction

  • Apply vendor kernel updates that include the AppArmor fix.
  • Review Debian LTS and distribution advisories for backported kernel packages.
  • Restrict AppArmor profile loading and replacement to trusted administrative paths.
  • Do not process untrusted AppArmor profile bundles on vulnerable systems.
  • If patch status is unclear, check current vendor guidance.

Validation and detection

  • Inventory Linux hosts where AppArmor is enabled.
  • Confirm kernel package versions include vendor backports or upstream stable fixes.
  • Check kernel logs for AppArmor-related general protection faults or NULL dereferences.
  • Review who or what can run apparmor_parser or replace profiles.
  • Test updated kernels in staging with normal AppArmor profile workflows.
Prepared
Confidence
medium
Sources
12

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-52443 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
11Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux04dc715e24d0820bf8740e1a1135ed61fe162bc8, 04dc715e24d0820bf8740e1a1135ed61fe162bc8, 04dc715e24d0820bf8740e1a1135ed61fe162bc8, 04dc715e24d0820bf8740e1a1135ed61fe162bc8, 04dc715e24d0820bf8740e1a1135ed61fe162bc8, 04dc715e24d0820bf8740e1a1135ed61fe162bc8, 04dc715e24d0820bf8740e1a1135ed61fe162bc8, 04dc715e24d0820bf8740e1a1135ed61fe162bc8unaffected
LinuxLinux4.11, 0, 4.19.306, 5.4.268, 5.10.209, 5.15.148, 6.1.75, 6.6.14, 6.7.2, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.