BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2023-52443High confidence

apparmor: avoid crash when parsed profile name is empty

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.24% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.6.15-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.76-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.6.15-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.6.15-1Debian Security Tracker ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2023-52443 · CSAF 2.0 · revision 62 · interimSUSE Product Security TeamCVE-2023-52443
109 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE CaaS Platform 4.0
  • kernel-default-base as component of SUSE CaaS Platform 4.0
  • kernel-default-devel as component of SUSE CaaS Platform 4.0
  • kernel-devel as component of SUSE CaaS Platform 4.0
  • kernel-macros as component of SUSE CaaS Platform 4.0
  • kernel-source as component of SUSE CaaS Platform 4.0
  • reiserfs-kmp-default as component of SUSE CaaS Platform 4.0
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
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: ? 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 ---[ 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).
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2023-57068

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

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

What

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

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

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

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → NULL Pointer Dereference → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Denial of serviceCWE-476
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-0473Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240228Security Bulletin 28 Feb 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 28 Feb 2024, published on 28 February 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0694Multiples vulnérabilités dans le noyau Linux d'Ubuntu

N-6957-1 du 13 août 2024 https://ubuntu.com/security/notices/USN-6957-1 Bulletin de sécurité Ubuntu USN-6951-2 du 14 août 2024 https://ubuntu.com/security/notices/USN-6951-2 Référence CVE CVE-2022-48674 https://www.cve.org/CVERecord?id=CVE-2022-48674 Référence CVE CVE-2022-48772 https://www.cve.org/CVERecord?id=CVE-2022-48772 Référence CVE CVE-2023-46343 https://www.cve.org/CVERecord?id=CVE-2023-46343 Référence CVE CVE-2023-52434 https://www.cve.org/CVERecord?id=CVE-2023-52434 Référence CVE CVE-2023-52435 https://www.cve.org/CVERecord?id=CVE-2023-52435 Référence CVE CVE-2023-52436 https://www.cve.org/CVERecord?id=CVE-2023-52436 Référence CVE CVE-2023-52443 https://www.cve.org/CVERecord?id=CVE-2023-52443 Référence CVE CVE-2023-52444 https://www.cve.org/CVERecord?id=CVE-2023-52444 Référence CVE CVE-2023-52449 https://www.cve.org/CVERecord?id=CVE-2023-52449 Référence CVE CVE-2023-52469 https://www.cve.org/CVERecord?id=CVE-2023-52469 Référence CVE CVE-2023-52585 https://www.cve.org/CVERecord?id=CVE-2023-52585 Référence CVE CVE-2023-52620 https://www.cve.org/CVERecord?id=CVE-2023-52620 Référence CVE CVE-2023-52752 https://www.cve.org/CVERecord?id=CVE-2023-52752 Référence CVE CVE-2023-52882 https://www.cve.org/CVERecord?id=CVE-2023-52882 Référence CVE CVE-2024-24857 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0667Multiples vulnérabilités dans le noyau Linux d'Ubuntu

/notices/USN-6953-1 Référence CVE CVE-2021-47131 https://www.cve.org/CVERecord?id=CVE-2021-47131 Référence CVE CVE-2022-48655 https://www.cve.org/CVERecord?id=CVE-2022-48655 Référence CVE CVE-2022-48674 https://www.cve.org/CVERecord?id=CVE-2022-48674 Référence CVE CVE-2022-48772 https://www.cve.org/CVERecord?id=CVE-2022-48772 Référence CVE CVE-2023-46343 https://www.cve.org/CVERecord?id=CVE-2023-46343 Référence CVE CVE-2023-52434 https://www.cve.org/CVERecord?id=CVE-2023-52434 Référence CVE CVE-2023-52435 https://www.cve.org/CVERecord?id=CVE-2023-52435 Référence CVE CVE-2023-52436 https://www.cve.org/CVERecord?id=CVE-2023-52436 Référence CVE CVE-2023-52443 https://www.cve.org/CVERecord?id=CVE-2023-52443 Référence CVE CVE-2023-52444 https://www.cve.org/CVERecord?id=CVE-2023-52444 Référence CVE CVE-2023-52449 https://www.cve.org/CVERecord?id=CVE-2023-52449 Référence CVE CVE-2023-52469 https://www.cve.org/CVERecord?id=CVE-2023-52469 Référence CVE CVE-2023-52585 https://www.cve.org/CVERecord?id=CVE-2023-52585 Référence CVE CVE-2023-52620 https://www.cve.org/CVERecord?id=CVE-2023-52620 Référence CVE CVE-2023-52631 https://www.cve.org/CVERecord?id=CVE-2023-52631 Référence CVE CVE-2023-52637 https://www.cve.org/CVERecord?id=CVE-2023-52637 Référence CVE CVE-2023-52638 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0645Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2021-47194 Référence CVE CVE-2022-38096 https://www.cve.org/CVERecord?id=CVE-2022-38096 Référence CVE CVE-2022-48619 https://www.cve.org/CVERecord?id=CVE-2022-48619 Référence CVE CVE-2022-48655 https://www.cve.org/CVERecord?id=CVE-2022-48655 Référence CVE CVE-2022-48808 https://www.cve.org/CVERecord?id=CVE-2022-48808 Référence CVE CVE-2023-46343 https://www.cve.org/CVERecord?id=CVE-2023-46343 Référence CVE CVE-2023-52434 https://www.cve.org/CVERecord?id=CVE-2023-52434 Référence CVE CVE-2023-52435 https://www.cve.org/CVERecord?id=CVE-2023-52435 Référence CVE CVE-2023-52436 https://www.cve.org/CVERecord?id=CVE-2023-52436 Référence CVE CVE-2023-52443 https://www.cve.org/CVERecord?id=CVE-2023-52443 Référence CVE CVE-2023-52444 https://www.cve.org/CVERecord?id=CVE-2023-52444 Référence CVE CVE-2023-52447 https://www.cve.org/CVERecord?id=CVE-2023-52447 Référence CVE CVE-2023-52449 https://www.cve.org/CVERecord?id=CVE-2023-52449 Référence CVE CVE-2023-52469 https://www.cve.org/CVERecord?id=CVE-2023-52469 Référence CVE CVE-2023-52488 https://www.cve.org/CVERecord?id=CVE-2023-52488 Référence CVE CVE-2023-52497 https://www.cve.org/CVERecord?id=CVE-2023-52497 Référence CVE CVE-2023-52620 https://www.cve.org/CVERecord?id=CVE-2023-52620 Référence CVE CVE-2023-52640 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0527Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2023-47233 Référence CVE CVE-2023-51779 https://www.cve.org/CVERecord?id=CVE-2023-51779 Référence CVE CVE-2023-52340 https://www.cve.org/CVERecord?id=CVE-2023-52340 Référence CVE CVE-2023-52429 https://www.cve.org/CVERecord?id=CVE-2023-52429 Référence CVE CVE-2023-52434 https://www.cve.org/CVERecord?id=CVE-2023-52434 Référence CVE CVE-2023-52435 https://www.cve.org/CVERecord?id=CVE-2023-52435 Référence CVE CVE-2023-52436 https://www.cve.org/CVERecord?id=CVE-2023-52436 Référence CVE CVE-2023-52438 https://www.cve.org/CVERecord?id=CVE-2023-52438 Référence CVE CVE-2023-52439 https://www.cve.org/CVERecord?id=CVE-2023-52439 Référence CVE CVE-2023-52443 https://www.cve.org/CVERecord?id=CVE-2023-52443 Référence CVE CVE-2023-52444 https://www.cve.org/CVERecord?id=CVE-2023-52444 Référence CVE CVE-2023-52445 https://www.cve.org/CVERecord?id=CVE-2023-52445 Référence CVE CVE-2023-52447 https://www.cve.org/CVERecord?id=CVE-2023-52447 Référence CVE CVE-2023-52448 https://www.cve.org/CVERecord?id=CVE-2023-52448 Référence CVE CVE-2023-52449 https://www.cve.org/CVERecord?id=CVE-2023-52449 Référence CVE CVE-2023-52451 https://www.cve.org/CVERecord?id=CVE-2023-52451 Référence CVE CVE-2023-52454 https://www.cve.org/CVERecord?id=CVE-2023-52454 Référence CVE CVE-2023-52456 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0383Multiples vulnérabilités dans le noyau Linux d'Ubuntu

uer un déni de service à distance, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données. Solution Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Ubuntu USN-6765-1 du 07 mai 2024 https://ubuntu.com/security/notices/USN-6765-1 Bulletin de sécurité Ubuntu USN-6766-1 du 07 mai 2024 https://ubuntu.com/security/notices/USN-6766-1 Bulletin de sécurité Ubuntu USN-6767-1 du 07 mai 2024 https://ubuntu.com/security/notices/USN-6767-1 Référence CVE CVE-2023-52435 https://www.cve.org/CVERecord?id=CVE-2023-52435 Référence CVE CVE-2023-52443 https://www.cve.org/CVERecord?id=CVE-2023-52443 Référence CVE CVE-2023-52444 https://www.cve.org/CVERecord?id=CVE-2023-52444 Référence CVE CVE-2023-52445 https://www.cve.org/CVERecord?id=CVE-2023-52445 Référence CVE CVE-2023-52446 https://www.cve.org/CVERecord?id=CVE-2023-52446 Référence CVE CVE-2023-52447 https://www.cve.org/CVERecord?id=CVE-2023-52447 Référence CVE CVE-2023-52448 https://www.cve.org/CVERecord?id=CVE-2023-52448 Référence CVE CVE-2023-52449 https://www.cve.org/CVERecord?id=CVE-2023-52449 Référence CVE CVE-2023-52450 https://www.cve.org/CVERecord?id=CVE-2023-52450 Référence CVE CVE-2023-52451 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0333Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2023-52340 Référence CVE CVE-2023-52429 https://www.cve.org/CVERecord?id=CVE-2023-52429 Référence CVE CVE-2023-52434 https://www.cve.org/CVERecord?id=CVE-2023-52434 Référence CVE CVE-2023-52435 https://www.cve.org/CVERecord?id=CVE-2023-52435 Référence CVE CVE-2023-52436 https://www.cve.org/CVERecord?id=CVE-2023-52436 Référence CVE CVE-2023-52438 https://www.cve.org/CVERecord?id=CVE-2023-52438 Référence CVE CVE-2023-52439 https://www.cve.org/CVERecord?id=CVE-2023-52439 Référence CVE CVE-2023-52441 https://www.cve.org/CVERecord?id=CVE-2023-52441 Référence CVE CVE-2023-52442 https://www.cve.org/CVERecord?id=CVE-2023-52442 Référence CVE CVE-2023-52443 https://www.cve.org/CVERecord?id=CVE-2023-52443 Référence CVE CVE-2023-52444 https://www.cve.org/CVERecord?id=CVE-2023-52444 Référence CVE CVE-2023-52445 https://www.cve.org/CVERecord?id=CVE-2023-52445 Référence CVE CVE-2023-52448 https://www.cve.org/CVERecord?id=CVE-2023-52448 Référence CVE CVE-2023-52449 https://www.cve.org/CVERecord?id=CVE-2023-52449 Référence CVE CVE-2023-52451 https://www.cve.org/CVERecord?id=CVE-2023-52451 Référence CVE CVE-2023-52454 https://www.cve.org/CVERecord?id=CVE-2023-52454 Référence CVE CVE-2023-52456 https://www.cve.org/CVERecord?id=CVE-2023-52456 Référence CVE CVE-2023-52457 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0301Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2023-52340 Référence CVE CVE-2023-52429 https://www.cve.org/CVERecord?id=CVE-2023-52429 Référence CVE CVE-2023-52434 https://www.cve.org/CVERecord?id=CVE-2023-52434 Référence CVE CVE-2023-52435 https://www.cve.org/CVERecord?id=CVE-2023-52435 Référence CVE CVE-2023-52436 https://www.cve.org/CVERecord?id=CVE-2023-52436 Référence CVE CVE-2023-52438 https://www.cve.org/CVERecord?id=CVE-2023-52438 Référence CVE CVE-2023-52439 https://www.cve.org/CVERecord?id=CVE-2023-52439 Référence CVE CVE-2023-52441 https://www.cve.org/CVERecord?id=CVE-2023-52441 Référence CVE CVE-2023-52442 https://www.cve.org/CVERecord?id=CVE-2023-52442 Référence CVE CVE-2023-52443 https://www.cve.org/CVERecord?id=CVE-2023-52443 Référence CVE CVE-2023-52444 https://www.cve.org/CVERecord?id=CVE-2023-52444 Référence CVE CVE-2023-52445 https://www.cve.org/CVERecord?id=CVE-2023-52445 Référence CVE CVE-2023-52448 https://www.cve.org/CVERecord?id=CVE-2023-52448 Référence CVE CVE-2023-52449 https://www.cve.org/CVERecord?id=CVE-2023-52449 Référence CVE CVE-2023-52451 https://www.cve.org/CVERecord?id=CVE-2023-52451 Référence CVE CVE-2023-52454 https://www.cve.org/CVERecord?id=CVE-2023-52454 Référence CVE CVE-2023-52456 https://www.cve.org/CVERecord?id=CVE-2023-52456 Référence CVE CVE-2023-52457 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0265Multiples vulnérabilités dans le noyau Linux de SUSE

ord?id=CVE-2023-39191 Référence CVE CVE-2023-46343 https://www.cve.org/CVERecord?id=CVE-2023-46343 Référence CVE CVE-2023-46813 https://www.cve.org/CVERecord?id=CVE-2023-46813 Référence CVE CVE-2023-51042 https://www.cve.org/CVERecord?id=CVE-2023-51042 Référence CVE CVE-2023-51779 https://www.cve.org/CVERecord?id=CVE-2023-51779 Référence CVE CVE-2023-5197 https://www.cve.org/CVERecord?id=CVE-2023-5197 Référence CVE CVE-2023-52340 https://www.cve.org/CVERecord?id=CVE-2023-52340 Référence CVE CVE-2023-52429 https://www.cve.org/CVERecord?id=CVE-2023-52429 Référence CVE CVE-2023-52439 https://www.cve.org/CVERecord?id=CVE-2023-52439 Référence CVE CVE-2023-52443 https://www.cve.org/CVERecord?id=CVE-2023-52443 Référence CVE CVE-2023-52445 https://www.cve.org/CVERecord?id=CVE-2023-52445 Référence CVE CVE-2023-52447 https://www.cve.org/CVERecord?id=CVE-2023-52447 Référence CVE CVE-2023-52448 https://www.cve.org/CVERecord?id=CVE-2023-52448 Référence CVE CVE-2023-52449 https://www.cve.org/CVERecord?id=CVE-2023-52449 Référence CVE CVE-2023-52451 https://www.cve.org/CVERecord?id=CVE-2023-52451 Référence CVE CVE-2023-52452 https://www.cve.org/CVERecord?id=CVE-2023-52452 Référence CVE CVE-2023-52456 https://www.cve.org/CVERecord?id=CVE-2023-52456 Référence CVE CVE-2023-52457 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0242Multiples vulnérabilités dans le noyau Linux de SUSE

ord?id=CVE-2022-48628 Référence CVE CVE-2023-28746 https://www.cve.org/CVERecord?id=CVE-2023-28746 Référence CVE CVE-2023-35827 https://www.cve.org/CVERecord?id=CVE-2023-35827 Référence CVE CVE-2023-46343 https://www.cve.org/CVERecord?id=CVE-2023-46343 Référence CVE CVE-2023-51042 https://www.cve.org/CVERecord?id=CVE-2023-51042 Référence CVE CVE-2023-5197 https://www.cve.org/CVERecord?id=CVE-2023-5197 Référence CVE CVE-2023-52340 https://www.cve.org/CVERecord?id=CVE-2023-52340 Référence CVE CVE-2023-52429 https://www.cve.org/CVERecord?id=CVE-2023-52429 Référence CVE CVE-2023-52439 https://www.cve.org/CVERecord?id=CVE-2023-52439 Référence CVE CVE-2023-52443 https://www.cve.org/CVERecord?id=CVE-2023-52443 Référence CVE CVE-2023-52445 https://www.cve.org/CVERecord?id=CVE-2023-52445 Référence CVE CVE-2023-52447 https://www.cve.org/CVERecord?id=CVE-2023-52447 Référence CVE CVE-2023-52448 https://www.cve.org/CVERecord?id=CVE-2023-52448 Référence CVE CVE-2023-52449 https://www.cve.org/CVERecord?id=CVE-2023-52449 Référence CVE CVE-2023-52451 https://www.cve.org/CVERecord?id=CVE-2023-52451 Référence CVE CVE-2023-52452 https://www.cve.org/CVERecord?id=CVE-2023-52452 Référence CVE CVE-2023-52456 https://www.cve.org/CVERecord?id=CVE-2023-52456 Référence CVE CVE-2023-52457 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0226Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2023-46838 Référence CVE CVE-2023-46862 https://www.cve.org/CVERecord?id=CVE-2023-46862 Référence CVE CVE-2023-50431 https://www.cve.org/CVERecord?id=CVE-2023-50431 Référence CVE CVE-2023-51779 https://www.cve.org/CVERecord?id=CVE-2023-51779 Référence CVE CVE-2023-51780 https://www.cve.org/CVERecord?id=CVE-2023-51780 Référence CVE CVE-2023-51782 https://www.cve.org/CVERecord?id=CVE-2023-51782 Référence CVE CVE-2023-52436 https://www.cve.org/CVERecord?id=CVE-2023-52436 Référence CVE CVE-2023-52438 https://www.cve.org/CVERecord?id=CVE-2023-52438 Référence CVE CVE-2023-52439 https://www.cve.org/CVERecord?id=CVE-2023-52439 Référence CVE CVE-2023-52443 https://www.cve.org/CVERecord?id=CVE-2023-52443 Référence CVE CVE-2023-52444 https://www.cve.org/CVERecord?id=CVE-2023-52444 Référence CVE CVE-2023-52445 https://www.cve.org/CVERecord?id=CVE-2023-52445 Référence CVE CVE-2023-52447 https://www.cve.org/CVERecord?id=CVE-2023-52447 Référence CVE CVE-2023-52448 https://www.cve.org/CVERecord?id=CVE-2023-52448 Référence CVE CVE-2023-52449 https://www.cve.org/CVERecord?id=CVE-2023-52449 Référence CVE CVE-2023-52451 https://www.cve.org/CVERecord?id=CVE-2023-52451 Référence CVE CVE-2023-52454 https://www.cve.org/CVERecord?id=CVE-2023-52454 Référence CVE CVE-2023-52456 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-026089Linux の Linux Kernel における NULL ポインタデリファレンスに関する脆弱性

Linux の Linux Kernel には、NULL ポインタデリファレンスに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Linux: < 4.11, 4.19.306 ≤ 4.19.*, 5.4.268 ≤ 5.4.*, 5.10.209 ≤ 5.10.*, 5.15.148 ≤ 5.15.*, 6.1.75 ≤ 6.1.*, 6.6.14 ≤ 6.6.*, 6.7.2 ≤ 6.7.*, 6.8 ≤ *
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 22 Feb 2024 · Last source change 11 May 2026, 19:27 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2023-57068
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2023-57068↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-52443 · cve.blacktree.nl