From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80920: io_uring: defer eventfd signaling when queued from a wakeup handler
Date: Wed, 9 Sep 2026 18:13:20 +0200 [thread overview]
Message-ID: <2026090915-CVE-2026-80920-9c6d@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
io_uring: defer eventfd signaling when queued from a wakeup handler
io_req_local_work_add() signals the CQ ring eventfd inline when it is the
one to push the first entry onto ->work_list. For DEFER_TASKRUN rings that
add is frequently done from a waitqueue wakeup handler, where an
arbitrary waitqueue lock is held.
eventfd_signal_mask() only refuses to recurse when current->in_eventfd
is set, but that bit is set by eventfd_signal_mask() itself. If the wake
chain starts somewhere else, signal goes out inline and can feed back
into epoll.
Add IOU_F_TWQ_IN_WAKE, set it on the task_work add done from the three
waitqueue callbacks, and use it to force io_eventfd_signal() down the
existing call_rcu_hurry() deferral instead of signaling inline.
The Linux kernel CVE team has assigned CVE-2026-80920 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.1 with commit 21a091b970cdbcf3e8ff829234b51be6f9192766 and fixed in 6.18.49 with commit e22f4494cc9487d326e5e3067f33dea7c1e442b2
Issue introduced in 6.1 with commit 21a091b970cdbcf3e8ff829234b51be6f9192766 and fixed in 7.1.11 with commit b6bb334b0e9348887e3e55e1f494b0c3b8fbf59f
Issue introduced in 6.1 with commit 21a091b970cdbcf3e8ff829234b51be6f9192766 and fixed in 7.2.1 with commit 40b6ccf68731809ceb85c6e9f0f8f2ed61c7aa5a
Issue introduced in 6.1 with commit 21a091b970cdbcf3e8ff829234b51be6f9192766 and fixed in 7.3-rc1 with commit cd305ee3633a45fcf5f3a5d83f99f3cb77d87b6e
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-80920
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
include/linux/io_uring_types.h
io_uring/eventfd.c
io_uring/eventfd.h
io_uring/futex.c
io_uring/io_uring.c
io_uring/poll.c
io_uring/tw.c
io_uring/waitid.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/e22f4494cc9487d326e5e3067f33dea7c1e442b2
https://git.kernel.org/stable/c/b6bb334b0e9348887e3e55e1f494b0c3b8fbf59f
https://git.kernel.org/stable/c/40b6ccf68731809ceb85c6e9f0f8f2ed61c7aa5a
https://git.kernel.org/stable/c/cd305ee3633a45fcf5f3a5d83f99f3cb77d87b6e
reply other threads:[~2026-09-09 16:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2026090915-CVE-2026-80920-9c6d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@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 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.