From: Greg KH <greg@kroah.com>
To: Paul Kramme <kramme@digitalmanufaktur.com>
Cc: stable@vger.kernel.org, john.johansen@canonical.com
Subject: Re: NULL pointer dereference in apparmor's profile_transition v6.12
Date: Tue, 21 Jan 2025 12:32:48 +0100 [thread overview]
Message-ID: <2025012142-resupply-stimulate-c3de@gregkh> (raw)
In-Reply-To: <CAHcPAXTDE-X28xU2ngUASXQdgrQdOAffSh1qYbPgS98u3mSKOA@mail.gmail.com>
On Tue, Jan 21, 2025 at 11:55:21AM +0100, Paul Kramme wrote:
> Hello,
>
> with v6.12 we encountered a kernel BUG (panic on our systems) that is
> caused by a NULL pointer dereference inside the apparmor's
> profile_transition code. I've contacted John Johansen as the
> maintainer for the apparmor system, and he pointed me to 17d0d04f3c99
> as a fix for that issue. That commit has now landed in v6.13, would it
> be possible to backport this to v6.12? Commit is
>
> 17d0d04f3c99 apparmor: allocate xmatch for nullpdb inside aa_alloc_null
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2025-01-21 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 10:55 NULL pointer dereference in apparmor's profile_transition v6.12 Paul Kramme
2025-01-21 11:32 ` Greg KH [this message]
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=2025012142-resupply-stimulate-c3de@gregkh \
--to=greg@kroah.com \
--cc=john.johansen@canonical.com \
--cc=kramme@digitalmanufaktur.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox