Local kernel panic via unset AppArmor socket label
Published Aug 17, 2024 · Updated May 11, 2026
NULL pointer dereference in AppArmor in affected Linux kernel releases allows local users to trigger a kernel panic during socket creation. A race delivers a secmarked ICMP packet before apparmor_socket_post_create() initializes SK_CTX(sk)->label, so apparmor_secmark_check() dereferences the null label. Reachability requires low-privileged local access and packet delivery during raw-socket creation; the demonstrated consequence is a kernel panic, without reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in AppArmor in affected Linux kernel releases allows local users to trigger a kernel panic during socket creation. A race delivers a secmarked ICMP packet before apparmor_socket_post_create() initializes SK_CTX(sk)->label, so apparmor_secmark_check() dereferences the null label. Reachability requires low-privileged local access and packet delivery during raw-socket creation; the demonstrated consequence is a kernel panic, without reported data disclosure or modification.
The record
- CVE
- CVE-2023-52889
- Published
- Aug 17, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 17, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.20
- Affected versionversion=ab9f2115081ab7ba63b77a759e0f3eb5d6463d7f <0abe35bc48d4ec80424b1f4b3560c0e082cbd5c1
- Affected versionversion=ab9f2115081ab7ba63b77a759e0f3eb5d6463d7f <290a6b88e8c19b6636ed1acc733d1458206f7697
- Affected versionversion=ab9f2115081ab7ba63b77a759e0f3eb5d6463d7f <347dcb84a4874b5fb375092c08d8cc4069b94f81
- Affected versionversion=ab9f2115081ab7ba63b77a759e0f3eb5d6463d7f <46c17ead5b7389e22e7dc9903fd0ba865d05bda2
- Affected versionversion=ab9f2115081ab7ba63b77a759e0f3eb5d6463d7f <6c920754f62cefc63fccdc38a062c7c3452e2961
- Affected versionversion=ab9f2115081ab7ba63b77a759e0f3eb5d6463d7f <ead2ad1d9f045f26fdce3ef1644913b3a6cd38f2
- Affected versionversion=ab9f2115081ab7ba63b77a759e0f3eb5d6463d7f <fce09ea314505a52f2436397608fa0a5d0934fb1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo