From: Peter Zijlstra <peterz@infradead.org>
To: Qing Wang <wangqing7171@gmail.com>
Cc: mathieu.desnoyers@efficios.com, dvyukov@google.com,
justinstitt@google.com, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, mark.rutland@arm.com, 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 12:42:55 +0200 [thread overview]
Message-ID: <20260602104255.GG4149641@noisy.programming.kicks-ass.net> (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),
> };
> ```
FWIW, I've no idea what that ``` nonsense is, but it does not belong in
Changelogs. I've removed it.
next prev parent reply other threads:[~2026-06-02 10:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 2:13 [PATCH] rseq: fix using an uninitialized stack variable in rseq_exit_user_update 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
2026-06-02 10:42 ` Peter Zijlstra [this message]
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-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=20260602104255.GG4149641@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dvyukov@google.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--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 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.