From: Qing Wang <wangqing7171@gmail.com>
To: Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Ingo Molnar <mingo@kernel.org>,
Dmitry Vyukov <dvyukov@google.com>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
Qing Wang <wangqing7171@gmail.com>,
syzbot+185a631927096f9da2fc@syzkaller.appspotmail.com
Subject: [PATCH] rseq: fix using an uninitialized stack variable in rseq_exit_user_update
Date: Mon, 1 Jun 2026 10:13:59 +0800 [thread overview]
Message-ID: <20260601021359.3679327-1-wangqing7171@gmail.com> (raw)
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>
---
include/linux/rseq_entry.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/rseq_entry.h b/include/linux/rseq_entry.h
index 63bc72086e75..e05f4c18f39e 100644
--- a/include/linux/rseq_entry.h
+++ b/include/linux/rseq_entry.h
@@ -638,8 +638,8 @@ static __always_inline bool rseq_exit_user_update(struct pt_regs *regs, struct t
struct rseq_ids ids = {
.cpu_id = task_cpu(t),
.mm_cid = task_mm_cid(t),
- .node_id = cpu_to_node(ids.cpu_id),
};
+ ids.node_id = cpu_to_node(ids.cpu_id);
return rseq_update_usr(t, regs, &ids);
efault:
--
2.34.1
next reply other threads:[~2026-06-01 2:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 2:13 Qing Wang [this message]
2026-06-01 13:59 ` [PATCH] rseq: fix using an uninitialized stack variable in rseq_exit_user_update 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
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
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=20260601021359.3679327-1-wangqing7171@gmail.com \
--to=wangqing7171@gmail.com \
--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=peterz@infradead.org \
--cc=syzbot+185a631927096f9da2fc@syzkaller.appspotmail.com \
--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