From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Oleg Nesterov <oleg@redhat.com>
Subject: [GIT PULL] timer subsystem fix
Date: Sat, 11 Jul 2026 13:23:03 +0200 [thread overview]
Message-ID: <alInly2mhGhYeZ4B@gmail.com> (raw)
Linus,
Please pull the latest timers/urgent Git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-2026-07-11
for you to fetch changes up to 920f893f735e92ba3a1cd9256899a186b161928d:
- Fix a subtle posix-cpu-timers vs. exec() race, which
unearthed other races in the area (Thomas Gleixner)
Thanks,
Ingo
------------------>
Thomas Gleixner (1):
posix-cpu-timers: Prevent UAF caused by non-leader exec() race
kernel/exit.c | 7 +-
kernel/signal.c | 10 ++-
kernel/time/posix-cpu-timers.c | 173 +++++++++++++++++++++++++++--------------
3 files changed, 130 insertions(+), 60 deletions(-)
next reply other threads:[~2026-07-11 11:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 11:23 Ingo Molnar [this message]
2026-07-11 17:14 ` [GIT PULL] timer subsystem fix pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2026-05-17 6:39 Ingo Molnar
2026-05-17 19:28 ` pr-tracker-bot
2026-05-09 2:01 Ingo Molnar
2026-05-09 3:32 ` pr-tracker-bot
2026-04-20 7:39 Ingo Molnar
2026-04-20 23:31 ` pr-tracker-bot
2026-03-29 5:27 Ingo Molnar
2026-03-29 17:29 ` pr-tracker-bot
2026-03-15 3:30 Ingo Molnar
2026-03-15 18:47 ` pr-tracker-bot
2026-03-08 0:49 Ingo Molnar
2026-03-08 1:23 ` pr-tracker-bot
2026-01-18 10:05 Ingo Molnar
2026-01-19 13:54 ` pr-tracker-bot
2025-11-15 9:13 Ingo Molnar
2025-11-15 18:26 ` pr-tracker-bot
2025-09-14 9:34 Ingo Molnar
2025-09-14 15:43 ` pr-tracker-bot
2025-09-07 10:35 Ingo Molnar
2025-09-07 15:32 ` pr-tracker-bot
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=alInly2mhGhYeZ4B@gmail.com \
--to=mingo@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=daniel.lezcano@linaro.org \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.