Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Li Zetao <lizetao1@huawei.com>,
	Robert Garcia <rob_garcia@163.com>,
	io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5.15.y] io_uring: prevent opcode speculation
Date: Wed, 20 May 2026 10:31:38 -0400	[thread overview]
Message-ID: <stable-reply-0003-io-uring-opcode-5.15@kernel.org> (raw)
In-Reply-To: <20260520062833.2563847-1-rob_garcia@163.com>

> From: Pavel Begunkov <asml.silence@gmail.com>
>
> [ Upstream commit 1e988c3fe1264708f4f92109203ac5b1d65de50b ]
>
> sqe->opcode is used for different tables, make sure we santitise it
> against speculations.
[...]
> [ Use req->opcode instead of opcode here. ]
> Signed-off-by: Robert Garcia <rob_garcia@163.com>

Thanks for the backport. Upstream 1e988c3fe126 is currently queued or
present on 6.6, 6.12, 6.18 and 7.0, but it is missing from both 5.15
and 6.1 - we should not skip 6.1 when backporting a Cc:stable fix to
5.15.

Could you send a matching backport for 6.1 as well? Once we have
coverage from 6.1 onwards I'll queue both together.

--
Thanks,
Sasha

      reply	other threads:[~2026-05-20 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20  6:28 [PATCH 5.15.y] io_uring: prevent opcode speculation Robert Garcia
2026-05-20 14:31 ` Sasha Levin [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=stable-reply-0003-io-uring-opcode-5.15@kernel.org \
    --to=sashal@kernel.org \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizetao1@huawei.com \
    --cc=rob_garcia@163.com \
    --cc=stable@vger.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