Description
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.
Product status
56974a6fcfef69ee0825bd66ed13e92070ac5224 (git) before 68538ec34fcb4194c7961dc4eca6f5537fec8067
56974a6fcfef69ee0825bd66ed13e92070ac5224 (git) before 5121b7283f1c46e4c06b88b1dda7b064429d77de
56974a6fcfef69ee0825bd66ed13e92070ac5224 (git) before c11b7c3280d000376e27ebfed17ec7046699eab4
56974a6fcfef69ee0825bd66ed13e92070ac5224 (git) before 0dc19bca22606f7a61d5988408f74e3ae0ef3486
56974a6fcfef69ee0825bd66ed13e92070ac5224 (git) before 3852eb9a0392eb435c03dcb47d581bcfe6a9a95b
56974a6fcfef69ee0825bd66ed13e92070ac5224 (git) before ccb66a3c6c8f51b3ed1bc003b70bb9ff99e8d835
56974a6fcfef69ee0825bd66ed13e92070ac5224 (git) before 8a0ededbfcff74598f82f1d4b8ef9db28878b317
56974a6fcfef69ee0825bd66ed13e92070ac5224 (git) before 00b67657535dfea56e84d11492f5c0f61d0af297
4.17
Any version before 4.17
5.10.252 (semver)
5.15.202 (semver)
6.1.165 (semver)
6.6.128 (semver)
6.12.75 (semver)
6.18.14 (semver)
6.19.4 (semver)
7.0 (original_commit_for_fix)
References
git.kernel.org/...c/68538ec34fcb4194c7961dc4eca6f5537fec8067
git.kernel.org/...c/5121b7283f1c46e4c06b88b1dda7b064429d77de
git.kernel.org/...c/c11b7c3280d000376e27ebfed17ec7046699eab4
git.kernel.org/...c/0dc19bca22606f7a61d5988408f74e3ae0ef3486
git.kernel.org/...c/3852eb9a0392eb435c03dcb47d581bcfe6a9a95b
git.kernel.org/...c/ccb66a3c6c8f51b3ed1bc003b70bb9ff99e8d835
git.kernel.org/...c/8a0ededbfcff74598f82f1d4b8ef9db28878b317
git.kernel.org/...c/00b67657535dfea56e84d11492f5c0f61d0af297