All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99796: io_uring/poll: cancel all matching requests in one pass
Date: Fri, 20 Nov 2026 08:02:15 +0100	[thread overview]
Message-ID: <2026112015-CVE-2026-99796-d677@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

io_uring/poll: cancel all matching requests in one pass

With IORING_ASYNC_CANCEL_ALL, __io_async_cancel() calls io_try_cancel()
until nothing is found, and io_poll_cancel() cancels one request per
call, starting each lookup at the beginning of the hash. A cancelled
request stays hashed until its task work runs, so every lookup walks
past the ones already cancelled. Cancelling K of N pending polls visits
about K*N/2 requests in one io_uring_enter(), with uring_lock held.

A single CANCEL_FD|ALL on 80000 polls on one eventfd takes 17.06s,
0.02s with this change. With voluntary preemption the soft lockup
watchdog fires:

  watchdog: BUG: soft lockup - CPU#1 stuck for 26s! [repro:100]
  RIP: 0010:io_cancel_req_match+0x19/0xa0
   io_poll_cancel+0x73/0x170
   io_try_cancel+0x7b/0xf0
   __io_async_cancel+0x41/0x110

Walk the hash once and cancel every match, as io_cancel_remove() does
for futex and waitid. Cancel by user_data only needs its own bucket.
__io_async_cancel() still loops until nothing is found, so a request
that io-wq parks in the poll hash meanwhile is still cancelled.

A cancel that matches one request now walks the whole hash twice instead
of stopping at the match.

The Linux kernel CVE team has assigned CVE-2026-99796 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.19 with commit 8e29da69feade64ec7fe9e1a2824b967c5183a21 and fixed in 6.12.118 with commit 9073da4d5bd87c71235d909512c478e8a13a5818
	Issue introduced in 5.19 with commit 8e29da69feade64ec7fe9e1a2824b967c5183a21 and fixed in 6.18.64 with commit 5310b477e619209b0cceb00b71ebc05a3e89360b
	Issue introduced in 5.19 with commit 8e29da69feade64ec7fe9e1a2824b967c5183a21 and fixed in 7.3.5 with commit e409e1b03059c544d271c7f8e1215c5c0c62f278
	Issue introduced in 5.19 with commit 8e29da69feade64ec7fe9e1a2824b967c5183a21 and fixed in 7.4-rc2 with commit 9eff9c07e927dcd9c57150cd6fb3d4ec76f00480

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-99796
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:
	io_uring/cancel.c
	io_uring/poll.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/9073da4d5bd87c71235d909512c478e8a13a5818
	https://git.kernel.org/stable/c/5310b477e619209b0cceb00b71ebc05a3e89360b
	https://git.kernel.org/stable/c/e409e1b03059c544d271c7f8e1215c5c0c62f278
	https://git.kernel.org/stable/c/9eff9c07e927dcd9c57150cd6fb3d4ec76f00480

                 reply	other threads:[~2026-11-20  7:02 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=2026112015-CVE-2026-99796-d677@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.