apparmor: fix NULL sock in aa_sock_file_perm
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 56974a6fcfef69ee0825bd66ed13e92070ac5224 · < ccb66a3c6c8f51b3ed1bc003b70bb9ff99e8d835| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The AppArmor socket permission check can dereference a NULL socket or socket state during socket setup or teardown, causing a kernel oops. The input does not establish how an attacker could trigger it or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with AppArmor should check their systems; affected versions are not specified.