Bug 2482188 (CVE-2026-45848) - CVE-2026-45848 kernel: apparmor: fix NULL sock in aa_sock_file_perm
Summary: CVE-2026-45848 kernel: apparmor: fix NULL sock in aa_sock_file_perm
Keywords:
Status: NEW
Alias: CVE-2026-45848
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-27 15:15 UTC by OSIDB Bzimport
Modified: 2026-05-28 05:02 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-05-27 15:15:30 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.