From: Jens Axboe <axboe@kernel.dk>
To: Kai Aizen <kai.aizen.dev@gmail.com>, stable@vger.kernel.org
Cc: gregkh@linuxfoundation.org, io-uring@vger.kernel.org
Subject: Re: [PATCH 6.12.y] io_uring/poll: fix multishot recv missing EOF on wakeup race
Date: Fri, 1 May 2026 16:55:54 -0600 [thread overview]
Message-ID: <3fcf1bf1-23fb-4e01-ac3d-6ec6fb86da08@kernel.dk> (raw)
In-Reply-To: <20260501225250.90152-1-kai.aizen.dev@gmail.com>
First of all, I'm fine backporting these. But:
> CVE: CVE-2026-23473
How on earth is this a CVE?! That's bogus. Yes it violates application
expectations, it'll wait on a CQE it won't get, potentially. But this is
the only side effect. That is NOT a CVE. Greg, please retract that.
--
Jens Axboe
prev parent reply other threads:[~2026-05-01 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 22:51 [PATCH 6.12.y] io_uring/poll: fix multishot recv missing EOF on wakeup race Kai Aizen
2026-05-01 22:51 ` [PATCH 6.6.y] " Kai Aizen
2026-05-01 22:51 ` [PATCH 6.1.y] " Kai Aizen
2026-05-01 22:51 ` [PATCH stable] io_uring/poll: ensure EPOLL_ONESHOT is propagated for EPOLL_URING_WAKE Kai Aizen
2026-05-01 22:56 ` Jens Axboe
2026-05-01 22:55 ` Jens Axboe [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=3fcf1bf1-23fb-4e01-ac3d-6ec6fb86da08@kernel.dk \
--to=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=io-uring@vger.kernel.org \
--cc=kai.aizen.dev@gmail.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