From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-45848: apparmor: fix NULL sock in aa_sock_file_perm
Date: Wed, 27 May 2026 14:18:10 +0200 [thread overview]
Message-ID: <2026052707-CVE-2026-45848-b001@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-45848 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.17 with commit 56974a6fcfef69ee0825bd66ed13e92070ac5224 and fixed in 5.10.252 with commit 68538ec34fcb4194c7961dc4eca6f5537fec8067
Issue introduced in 4.17 with commit 56974a6fcfef69ee0825bd66ed13e92070ac5224 and fixed in 5.15.202 with commit 5121b7283f1c46e4c06b88b1dda7b064429d77de
Issue introduced in 4.17 with commit 56974a6fcfef69ee0825bd66ed13e92070ac5224 and fixed in 6.1.165 with commit c11b7c3280d000376e27ebfed17ec7046699eab4
Issue introduced in 4.17 with commit 56974a6fcfef69ee0825bd66ed13e92070ac5224 and fixed in 6.6.128 with commit 0dc19bca22606f7a61d5988408f74e3ae0ef3486
Issue introduced in 4.17 with commit 56974a6fcfef69ee0825bd66ed13e92070ac5224 and fixed in 6.12.75 with commit 3852eb9a0392eb435c03dcb47d581bcfe6a9a95b
Issue introduced in 4.17 with commit 56974a6fcfef69ee0825bd66ed13e92070ac5224 and fixed in 6.18.14 with commit ccb66a3c6c8f51b3ed1bc003b70bb9ff99e8d835
Issue introduced in 4.17 with commit 56974a6fcfef69ee0825bd66ed13e92070ac5224 and fixed in 6.19.4 with commit 8a0ededbfcff74598f82f1d4b8ef9db28878b317
Issue introduced in 4.17 with commit 56974a6fcfef69ee0825bd66ed13e92070ac5224 and fixed in 7.0 with commit 00b67657535dfea56e84d11492f5c0f61d0af297
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-45848
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
security/apparmor/net.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/68538ec34fcb4194c7961dc4eca6f5537fec8067
https://git.kernel.org/stable/c/5121b7283f1c46e4c06b88b1dda7b064429d77de
https://git.kernel.org/stable/c/c11b7c3280d000376e27ebfed17ec7046699eab4
https://git.kernel.org/stable/c/0dc19bca22606f7a61d5988408f74e3ae0ef3486
https://git.kernel.org/stable/c/3852eb9a0392eb435c03dcb47d581bcfe6a9a95b
https://git.kernel.org/stable/c/ccb66a3c6c8f51b3ed1bc003b70bb9ff99e8d835
https://git.kernel.org/stable/c/8a0ededbfcff74598f82f1d4b8ef9db28878b317
https://git.kernel.org/stable/c/00b67657535dfea56e84d11492f5c0f61d0af297
reply other threads:[~2026-05-27 12:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026052707-CVE-2026-45848-b001@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.