From: John Johansen <john.johansen@canonical.com>
To: Jann Horn <jannh@google.com>, John Johansen <john@apparmor.net>,
Georgia Garcia <georgia.garcia@canonical.com>,
apparmor@lists.ubuntu.com, Paul Moore <paul@paul-moore.com>,
"Serge E. Hallyn" <serge@hallyn.com>
Cc: James Morris <jmorris@namei.org>,
Christian Brauner <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
kernel list <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] apparmor: fix cred UAF caused by begin_current_label_crit_section()
Date: Wed, 5 Aug 2026 16:13:35 -0700 [thread overview]
Message-ID: <97987e10-07bd-4f06-8b64-e3e076aef33f@canonical.com> (raw)
In-Reply-To: <CAG48ez31uJ1utneG2VepgkpYp-zpmypoBJ5TTXOxiPLrZsXTrQ@mail.gmail.com>
On 8/5/26 08:10, Jann Horn wrote:
> On Tue, Jul 14, 2026 at 5:39 PM Jann Horn <jannh@google.com> wrote:
>> AppArmor's begin_current_label_crit_section() is a scary function called
>> from lots of LSM hooks (in particular VFS/socket-related ones) that checks
>> if the label referenced by the current creds is marked FLAG_STALE, and if
>> so, attempts to use aa_replace_current_label() to replace the creds with an
>> updated version that uses a new label.
>
> ping, I've seen no activity on this fix since posting it
sorry, just swamped and not catching up so far.
I am looking at it now
next prev parent reply other threads:[~2026-08-05 23:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 15:38 Jann Horn
2026-07-14 15:49 ` Jann Horn
2026-08-05 15:10 ` Jann Horn
2026-08-05 23:13 ` John Johansen [this message]
2026-08-06 0:02 ` John Johansen
2026-08-06 13:14 ` Jann Horn
2026-08-06 7:32 ` Peter Zijlstra
2026-08-06 8:06 ` John Johansen
2026-08-06 13:11 ` Jann Horn
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=97987e10-07bd-4f06-8b64-e3e076aef33f@canonical.com \
--to=john.johansen@canonical.com \
--cc=apparmor@lists.ubuntu.com \
--cc=brauner@kernel.org \
--cc=georgia.garcia@canonical.com \
--cc=jannh@google.com \
--cc=jmorris@namei.org \
--cc=john@apparmor.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=peterz@infradead.org \
--cc=serge@hallyn.com \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®