From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andy Lutomirski <luto@kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Kees Cook <kees@kernel.org>,
Kusaram Devineni <kusaram@devineni.in>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@kernel.org>, Will Drewry <wad@chromium.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 3/3] signal: fix evasion of SA_IMMUTABLE signals
Date: Fri, 19 Jun 2026 15:28:09 +0200 [thread overview]
Message-ID: <ajVD6ZmiSQLxjj57@redhat.com> (raw)
In-Reply-To: <ajVDrvY01xRW2x72@redhat.com>
force_sig_info_to_task(HANDLER_EXIT) sets SA_IMMUTABLE to ensure a forced
fatal signal cannot be ignored or caught by userspace; it must always
terminate the target. However, if get_signal() dequeues another synchronous
signal first, and that signal has a handler and its sa_mask includes the
fatal SA_IMMUTABLE signal, the task can return to userspace and survive.
So dequeue_synchronous_signal() must always dequeue an SA_IMMUTABLE signal
first. But it relies on the SI_FROMKERNEL() check and picks the first one
it sees in pending->list, and thus we have the following problems:
- If the same signal was already pending and blocked, the new siginfo
with .si_code > 0 will be lost.
Change __send_signal_locked() to bypass the legacy_queue() check in
this case.
- If force_sig_info_to_task() races with another synchronous/SI_FROMKERNEL
signal, that signal can be picked first.
Change __send_signal_locked() to add an SA_IMMUTABLE signal at the start
of pending->list.
- SA_IMMUTABLE implies override_rlimit == true, but GFP_ATOMIC can fail
anyway.
Change __send_signal_locked() to escalate to SIGKILL in this (very
unlikely) case.
Not perfect and perhaps deserves WARN() or pr_warn_ratelimited(), but
better than nothing.
However, unlike get_signal(), __send_signal_locked() can not rely on the
k_sigaction.sa.sa_flags & SA_IMMUTABLE check; another signal with the same
.si_signo can come before dequeue_synchronous_signal() dequeues the signal
sent by force(HANDLER_EXIT). Say, send_sig_perf() from task_work_run(),
and this signal is SI_FROMKERNEL() too.
Use the new SEND_SIGNAL_IMMUTABLE flag to pass the "immutable" state from
force_sig_info_to_task() to __send_signal_locked().
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
---
kernel/signal.c | 24 ++++++++++++++++++------
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
index 9c607a598ba1..077effd21582 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -1038,10 +1038,12 @@ static inline bool legacy_queue(struct sigpending *signals, int sig)
}
#define SEND_SIGNAL_FORCE (1 << 0)
+#define SEND_SIGNAL_IMMUTABLE (1 << 1)
static int __send_signal_locked(int sig, struct kernel_siginfo *info,
struct task_struct *t, enum pid_type type, int flags)
{
+ bool immutable = flags & SEND_SIGNAL_IMMUTABLE;
struct sigpending *pending;
struct sigqueue *q;
int override_rlimit;
@@ -1055,12 +1057,12 @@ static int __send_signal_locked(int sig, struct kernel_siginfo *info,
pending = (type != PIDTYPE_PID) ? &t->signal->shared_pending : &t->pending;
/*
- * Short-circuit ignored signals and support queuing
- * exactly one non-rt signal, so that we can get more
- * detailed information about the cause of the signal.
+ * Queue exactly one non-rt signal so that we can get more
+ * detailed information about the cause. But we must never
+ * lose the siginfo for an SA_IMMUTABLE signal.
*/
result = TRACE_SIGNAL_ALREADY_PENDING;
- if (legacy_queue(pending, sig))
+ if (legacy_queue(pending, sig) && !immutable)
goto ret;
result = TRACE_SIGNAL_DELIVERED;
@@ -1087,7 +1089,12 @@ static int __send_signal_locked(int sig, struct kernel_siginfo *info,
q = sigqueue_alloc(sig, t, GFP_ATOMIC, override_rlimit);
if (q) {
- list_add_tail(&q->list, &pending->list);
+ /* Ensure dequeue_synchronous_signal() sees SA_IMMUTABLE first */
+ if (immutable)
+ list_add(&q->list, &pending->list);
+ else
+ list_add_tail(&q->list, &pending->list);
+
switch ((unsigned long) info) {
case (unsigned long) SEND_SIG_NOINFO:
clear_siginfo(&q->info);
@@ -1130,6 +1137,9 @@ static int __send_signal_locked(int sig, struct kernel_siginfo *info,
* send the signal, but the *info bits are lost.
*/
result = TRACE_SIGNAL_LOSE_INFO;
+ /* The task must not escape SA_IMMUTABLE; escalate to SIGKILL */
+ if (immutable)
+ sig = SIGKILL;
}
out_set:
@@ -1307,8 +1317,10 @@ force_sig_info_to_task(struct kernel_siginfo *info, struct task_struct *t,
blocked = sigismember(&t->blocked, sig);
if (blocked || ignored || (handler != HANDLER_CURRENT)) {
action->sa.sa_handler = SIG_DFL;
- if (handler == HANDLER_EXIT)
+ if (handler == HANDLER_EXIT) {
action->sa.sa_flags |= SA_IMMUTABLE;
+ send_flags |= SEND_SIGNAL_IMMUTABLE;
+ }
if (blocked)
sigdelset(&t->blocked, sig);
}
--
2.52.0
prev parent reply other threads:[~2026-06-19 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 13:27 [PATCH v2 1/3] signal: change force_sig_info_to_task() to call __send_signal_locked() Oleg Nesterov
2026-06-19 13:27 ` [PATCH v2 2/3] signal: turn the "bool force" arg of __send_signal_locked() into "int flags" Oleg Nesterov
2026-06-19 13:28 ` Oleg Nesterov [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=ajVD6ZmiSQLxjj57@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=kees@kernel.org \
--cc=kusaram@devineni.in \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=wad@chromium.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