From: Sasha Levin <sashal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"io-uring@vger.kernel.org" <io-uring@vger.kernel.org>,
Yufan Chen <yufan.chen@linux.dev>,
dev@rebasedinc.com
Subject: Re: io_uring/eventfd: registered eventfd signals only once after the cd305ee3633a backport (6.18.y, 6.12.y, Ubuntu 26.04)
Date: Tue, 17 Nov 2026 07:59:02 -0500 [thread overview]
Message-ID: <avxPlrd77WiXagvs@laps> (raw)
In-Reply-To: <8e6c1d69-9910-4c89-832a-34ecd65a0ca7@kernel.dk>
On Tue, Nov 17, 2026 at 05:45:53AM -0700, Jens Axboe wrote:
>On 11/17/26 5:42 AM, Sasha Levin wrote:
>> On Mon, Nov 16, 2026 at 07:21:38PM -0700, Jens Axboe wrote:
>>> On 11/16/26 2:52 AM, Greg Kroah-Hartman wrote:
>>>> On Sat, Nov 14, 2026 at 11:12:40AM -0700, Jens Axboe wrote:
>>>>> On 11/14/26 10:42 AM, Sasha Levin wrote:
>>>>>> On 2026-11-13, dev@rebasedinc.com wrote:
>>>>>>> If this is correct, a backport of 04fe9aeb4f3c to 6.18.y and 6.12.y looks like the right fix; it keeps the CVE-2026-80920 fix in place.
>>>>>>
>>>>>> Queued for 6.18 and 6.12, thanks.
>>>>>
>>>>> Yet another bs CVE - Greg, please invalidate this one too, it's NOT CVE material.
>>>>> Getting a little tired of chasing these.
>>>>
>>>> Now rejected, sorry about that.
>>>
>>> Not sure how we improve on that, it's really annoying to catch these bogus
>>> ones after the fact?
>>
>> Hi Jens,
>>
>> Since some of our reviews are LLM based, I was looking to see why this one was
>> flagged as a security issue.
>>
>> From the explanation, and looking at the code, it seems that we can register an
>> eventfd with io_uring, then have epoll watch that same eventfd. When something
>> wakes the epoll, the kernel is holding epoll's wait-queue lock. That wakeup
>> runs io_uring's poll handler, which signals the eventfd, but the eventfd is
>> watched by the same epoll, so it tries to grab that same lock again on the same
>> CPU. The CPU spins forever on a lock it already holds. One core is dead,
>> followed by RCU stalls, machine wedges. Any unprivileged user with io_uring
>> access can do it.
>
>I think you're looking at the parent of that, not the followup. Yes the
>parent is a real fix, it's similar to the eventfd fix in mainline as well
>for that exact issue.
If by followup you mean 04fe9aeb4f3c ("io_uring/eventfd: reset deferred signal
state") then yes, I don't think it's security relevant, and it never had a CVE
assigned.
cd305ee3633a ("io_uring: defer eventfd signaling when queued from a wakeup
handler") is what had the CVE assigned to it, and what Greg rejected earlier.
Should the rejection be reverted then?
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-17 12:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 23:22 Subject: io_uring/eventfd: registered eventfd signals only once after the cd305ee3633a backport (6.18.y, 6.12.y, Ubuntu 26.04) dev
2026-11-14 2:00 ` Greg KH
2026-11-15 1:13 ` dev
2026-11-14 17:42 ` Sasha Levin
2026-11-14 18:12 ` Jens Axboe
2026-11-16 9:52 ` Greg Kroah-Hartman
2026-11-17 2:21 ` Jens Axboe
2026-11-17 7:42 ` Greg Kroah-Hartman
2026-11-17 12:41 ` Jens Axboe
2026-11-17 12:42 ` Sasha Levin
2026-11-17 12:45 ` Jens Axboe
2026-11-17 12:59 ` 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=avxPlrd77WiXagvs@laps \
--to=sashal@kernel.org \
--cc=axboe@kernel.dk \
--cc=dev@rebasedinc.com \
--cc=gregkh@linuxfoundation.org \
--cc=io-uring@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yufan.chen@linux.dev \
/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.