From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>,
Thomas Gleixner <tglx@kernel.org>, Wongi Lee <qw3rtyp0@gmail.com>,
Jungwoo Lee <jwlee2217@gmail.com>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: RFC: How to backport 920f893f735e ("posix-cpu-timers: Prevent UAF caused by non-leader exec() race") down to 5.15.y?
Date: Tue, 21 Jul 2026 16:10:58 +0200 [thread overview]
Message-ID: <2026072148-saggy-broken-3ee6@gregkh> (raw)
In-Reply-To: <alVfR78eqdaRbOIy@eldamar.lan>
On Mon, Jul 13, 2026 at 11:57:27PM +0200, Salvatore Bonaccorso wrote:
> Hi,
>
> 920f893f735e ("posix-cpu-timers: Prevent UAF caused by non-leader
> exec() race") talks about a UAF, and the commit was CC'ed for stable.
> While checking it I noticed the commit though won't apply cleanly. I
> was thinking of needing to pick 6fdb2677a594 ("posix-timers: Expand
> timer_[re]arm() callbacks with a boolean return value") beforehand as
> preparatory change, and then 920f893f735e ("posix-cpu-timers: Prevent
> UAF caused by non-leader exec() race"). Would that be sound/sensible?
>
> At least that would apply cleanly (though not yet even compile tested)
> to 7.1.y and 6.18.y but then already not anymore to 6.12.y, which will
> need more adjustments.
>
> Thomas, would you intend to provide backports from you directly?
>
> The two patches reflect this RFC.
These look sane, I've queued them up now, thanks!
greg k-h
next prev parent reply other threads:[~2026-07-21 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 21:57 RFC: How to backport 920f893f735e ("posix-cpu-timers: Prevent UAF caused by non-leader exec() race") down to 5.15.y? Salvatore Bonaccorso
2026-07-21 14:10 ` Greg Kroah-Hartman [this message]
2026-07-22 0:53 ` Sasha Levin
2026-07-22 5:03 ` Salvatore Bonaccorso
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=2026072148-saggy-broken-3ee6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=carnil@debian.org \
--cc=jwlee2217@gmail.com \
--cc=oleg@redhat.com \
--cc=qw3rtyp0@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@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