CVE-2026-45848
apparmor: fix NULL sock in aa_sock_file_perm
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: apparmor: fix NULL sock in aa_sock_file_perm Deal with the potential that sock and sock-sk can be NULL during socket setup or teardown. This could lead to an oops. The fix for NULL pointer dereference in __unix_needs_revalidation shows this is at least possible for af_unix sockets. While the fix for af_unix sockets applies for newer mediation this is still the fall back path for older af_unix mediation and other sockets, so ensure it is covered.
Timeline
- CVE published
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.17
References 8
git.kernel.org
- stable/c/68538ec34fcb4194c7961dc4eca6f5537fec8067
- stable/c/5121b7283f1c46e4c06b88b1dda7b064429d77de
- stable/c/c11b7c3280d000376e27ebfed17ec7046699eab4
- stable/c/0dc19bca22606f7a61d5988408f74e3ae0ef3486
- stable/c/3852eb9a0392eb435c03dcb47d581bcfe6a9a95b
- stable/c/ccb66a3c6c8f51b3ed1bc003b70bb9ff99e8d835
- stable/c/8a0ededbfcff74598f82f1d4b8ef9db28878b317
- stable/c/00b67657535dfea56e84d11492f5c0f61d0af297