Kernel crash via unchecked socket pointers
Published May 27, 2026 · Updated May 27, 2026
NULL pointer dereference in Linux Kernel AppArmor allows local users to crash the kernel during socket setup or teardown. aa_sock_file_perm assumes file->private_data and the referenced socket's sk member are valid, then dereferences them without checking for NULL. Reachability requires a local low-privileged user to hit the AppArmor socket-file fallback path while a socket is being initialized or destroyed; the reported consequence is an availability-only kernel oops.
Summary
What happened
NULL pointer dereference in Linux Kernel AppArmor allows local users to crash the kernel during socket setup or teardown. aa_sock_file_perm assumes file->private_data and the referenced socket's sk member are valid, then dereferences them without checking for NULL. Reachability requires a local low-privileged user to hit the AppArmor socket-file fallback path while a socket is being initialized or destroyed; the reported consequence is an availability-only kernel oops.
The record
- CVE
- CVE-2026-45848
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 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.17
- Affected versionversion=56974a6fcfef69ee0825bd66ed13e92070ac5224 <00b67657535dfea56e84d11492f5c0f61d0af297
- Affected versionversion=56974a6fcfef69ee0825bd66ed13e92070ac5224 <0dc19bca22606f7a61d5988408f74e3ae0ef3486
- Affected versionversion=56974a6fcfef69ee0825bd66ed13e92070ac5224 <3852eb9a0392eb435c03dcb47d581bcfe6a9a95b
- Affected versionversion=56974a6fcfef69ee0825bd66ed13e92070ac5224 <5121b7283f1c46e4c06b88b1dda7b064429d77de
- Affected versionversion=56974a6fcfef69ee0825bd66ed13e92070ac5224 <68538ec34fcb4194c7961dc4eca6f5537fec8067
- Affected versionversion=56974a6fcfef69ee0825bd66ed13e92070ac5224 <8a0ededbfcff74598f82f1d4b8ef9db28878b317
- Affected versionversion=56974a6fcfef69ee0825bd66ed13e92070ac5224 <c11b7c3280d000376e27ebfed17ec7046699eab4
- Affected versionversion=56974a6fcfef69ee0825bd66ed13e92070ac5224 <ccb66a3c6c8f51b3ed1bc003b70bb9ff99e8d835
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.
Weakness, pattern, technique
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