From: Mark Rutland <mark.rutland@arm.com>
To: Qing Wang <wangqing7171@gmail.com>
Cc: peterz@infradead.org, mathieu.desnoyers@efficios.com,
dvyukov@google.com, justinstitt@google.com,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
mingo@kernel.org, morbo@google.com, nathan@kernel.org,
nick.desaulniers+lkml@gmail.com,
syzbot+185a631927096f9da2fc@syzkaller.appspotmail.com,
tglx@kernel.org
Subject: Re: [PATCH v2] rseq: fix using an uninitialized stack variable in rseq_exit_user_update
Date: Tue, 2 Jun 2026 11:08:30 +0100 [thread overview]
Message-ID: <ah6rnmm1ZpGRbOIR@J2N7QTR9R3> (raw)
In-Reply-To: <20260602030854.574038-1-wangqing7171@gmail.com>
On Tue, Jun 02, 2026 at 11:08:54AM +0800, Qing Wang wrote:
> There is an bug which is an uninitialized stack variable use in
> `rseq_exit_user_update()` reported by syzbot:
>
> BUG: KMSAN: kernel-infoleak in rseq_set_ids_get_csaddr include/linux/rseq_entry.h:502 [inline]
>
> The local variable:
> ```c
> struct rseq_ids ids = {
> .cpu_id = task_cpu(t),
> .mm_cid = task_mm_cid(t),
> .node_id = cpu_to_node(ids.cpu_id),
> };
> ```
> According to the C standard, the evaluation order of expressions in an
> initializer list is indeterminately sequenced. The compiler (Clang, in this
> KMSAN build) evaluates `cpu_to_node(ids.cpu_id)` *before* `ids.cpu_id` is
> initialized with `task_cpu(t)`.
>
> This is fixed by moving the assignment of ids.node_id outside the structure
> initialization.
>
> Reported-by: syzbot+185a631927096f9da2fc@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=185a631927096f9da2fc
> Fixes: 82f572449cfe ("rseq: Implement read only ABI enforcement for optimized RSEQ V2 mode")
> Signed-off-by: Qing Wang <wangqing7171@gmail.com>
FWIW, this looks sane to me, so:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
> ---
> include/linux/rseq_entry.h | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/rseq_entry.h b/include/linux/rseq_entry.h
> index 63bc72086e75..ed9da6e41a2a 100644
> --- a/include/linux/rseq_entry.h
> +++ b/include/linux/rseq_entry.h
> @@ -635,10 +635,11 @@ static __always_inline bool rseq_exit_user_update(struct pt_regs *regs, struct t
> return true;
> }
>
> + int cpu = task_cpu(t);
> struct rseq_ids ids = {
> - .cpu_id = task_cpu(t),
> + .cpu_id = cpu,
> .mm_cid = task_mm_cid(t),
> - .node_id = cpu_to_node(ids.cpu_id),
> + .node_id = cpu_to_node(cpu),
> };
>
> return rseq_update_usr(t, regs, &ids);
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-06-02 10:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 2:13 [PATCH] " Qing Wang
2026-06-01 13:59 ` Mathieu Desnoyers
2026-06-01 14:39 ` Peter Zijlstra
2026-06-02 3:08 ` [PATCH v2] " Qing Wang
2026-06-02 10:08 ` Mark Rutland [this message]
2026-06-02 10:42 ` Peter Zijlstra
2026-06-19 12:45 ` Tetsuo Handa
2026-06-19 19:32 ` Thomas Gleixner
2026-06-19 22:34 ` Tetsuo Handa
2026-06-20 19:51 ` Thomas Gleixner
2026-06-25 9:18 ` Alexander Potapenko
2026-06-02 10:45 ` [tip: sched/urgent] rseq: Fix using an uninitialized stack variable in rseq_exit_user_update() tip-bot2 for Qing Wang
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=ah6rnmm1ZpGRbOIR@J2N7QTR9R3 \
--to=mark.rutland@arm.com \
--cc=dvyukov@google.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=peterz@infradead.org \
--cc=syzbot+185a631927096f9da2fc@syzkaller.appspotmail.com \
--cc=tglx@kernel.org \
--cc=wangqing7171@gmail.com \
/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®