From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99804: io_uring/io-wq: save worker type before dropping its reference
Date: Fri, 20 Nov 2026 08:02:23 +0100 [thread overview]
Message-ID: <2026112018-CVE-2026-99804-a2ce@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
io_uring/io-wq: save worker type before dropping its reference
io_wq_cancel_tw_create() inspects cb->func after calling
io_worker_cancel_cb(). For an existing worker, that call can drop the
last worker reference and wake io_worker_exit(). If the canceling task
is preempted, the worker can be unlinked and freed by kfree_rcu() before
the callback function is inspected. KASAN reports a slab-use-after-free
read in this path.
Save whether the callback belongs to an unpublished continuation worker
while its reference is still held, then use the saved result for the
conditional free. This preserves the existing accounting and frees only
the worker allocated for the canceled continuation.
The Linux kernel CVE team has assigned CVE-2026-99804 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.2 with commit e6db6f9398dadcbc06318a133d4c44a2d3844e61 and fixed in 6.12.117 with commit 9d7af67e5425ad08d1ab9bbf4a3ad987d7871834
Issue introduced in 6.2 with commit e6db6f9398dadcbc06318a133d4c44a2d3844e61 and fixed in 6.18.61 with commit 2efcf743664ab4a83b4fae1f152bbea1d298e73f
Issue introduced in 6.2 with commit e6db6f9398dadcbc06318a133d4c44a2d3844e61 and fixed in 7.3.2 with commit 11239f2b509cd09d76c564b5fe262c70bad8ea3c
Issue introduced in 6.2 with commit e6db6f9398dadcbc06318a133d4c44a2d3844e61 and fixed in 7.4-rc1 with commit 37e425460b7c41687e51e3254b1eb1d799da9614
Issue introduced in 5.10.164 with commit a88a0d16e18f18d7221f0c5a1fdf487f5f9079e3
Issue introduced in 5.15.89 with commit ba86db02d408ae362ee5f1cde52ffafb37b41ce5
Issue introduced in 6.1.7 with commit e62e6258ab140b55bbef1f0d288263b75e2f0c20
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-99804
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/io-wq.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/9d7af67e5425ad08d1ab9bbf4a3ad987d7871834
https://git.kernel.org/stable/c/2efcf743664ab4a83b4fae1f152bbea1d298e73f
https://git.kernel.org/stable/c/11239f2b509cd09d76c564b5fe262c70bad8ea3c
https://git.kernel.org/stable/c/37e425460b7c41687e51e3254b1eb1d799da9614
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=2026112018-CVE-2026-99804-a2ce@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.