From: Greg KH <gregkh@linuxfoundation.org>
To: Carlo Conti <carlottoconti344@gmail.com>
Cc: axboe@kernel.dk, io-uring@vger.kernel.org
Subject: Re: [SECURITY] io_uring UAF: io_uring_cmd_issue_blocking missing sqe copy before RESIZE_RINGS
Date: Mon, 4 May 2026 14:10:17 +0200 [thread overview]
Message-ID: <2026050401-juniper-undocked-190c@gregkh> (raw)
In-Reply-To: <CAAiJJe3rVHjEO6yZ=w6S0igYFE8ROBay+An7PnuMX0KndxwXOg@mail.gmail.com>
On Mon, May 04, 2026 at 01:59:01PM +0200, Carlo Conti wrote:
> Hello,
>
> I have identified a Use-After-Free vulnerability in the Linux kernel
> io_uring subsystem, confirmed on Linux 6.19.11.
That is an unsupported and obsolete kernel version, does this happen on
the latest 7.0 release?
And can you provide a patch to fix this issue as you seem to be able to
test this?
Also, you sent this to a public mailing list, so I'll take security@k.o
off the response now as it's not needed.
thanks,
greg k-h
next parent reply other threads:[~2026-05-04 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAiJJe3rVHjEO6yZ=w6S0igYFE8ROBay+An7PnuMX0KndxwXOg@mail.gmail.com>
2026-05-04 12:10 ` Greg KH [this message]
2026-05-04 12:16 ` [SECURITY] io_uring UAF: io_uring_cmd_issue_blocking missing sqe copy before RESIZE_RINGS Jens Axboe
2026-05-04 12:29 ` Jens Axboe
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=2026050401-juniper-undocked-190c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=carlottoconti344@gmail.com \
--cc=io-uring@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