From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Cyber_black <Cyberblackk@proton.me>
Cc: "io-uring@vger.kernel.org" <io-uring@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"gabriel@krisman.be" <gabriel@krisman.be>
Subject: Re: [BUG] io_uring: possible CQE32 overflow flush inconsistency in __io_cqring_overflow_flush()
Date: Sat, 20 Jun 2026 08:17:41 +0200 [thread overview]
Message-ID: <2026062012-iphone-chasing-61e7@gregkh> (raw)
In-Reply-To: <Zurr63tEcYPbtU0ltI3-1KdtzFeys4ybMi-njjblykGD6LnMs7gYFwRzZNw3AbjYglMSO8LESxjUPHLnV2-AXHNa_17pDLHe9eCKTXBozLE=@proton.me>
On Sat, Jun 20, 2026 at 06:13:50AM +0000, Cyber_black wrote:
>
>
> Hi Gabriel,
>
> Thank you for your response.
>
> I found this bug while doing independent research. I was reading the Linux kernel code from Linus Torvalds' main repository (git.kernel.org) and the io_uring subsystem caught my attention. In particular, the use of shared memory for optimization purposes stood out – especially since this very feature has been exploited in the past to develop rootkits targeting io_uring.
>
> So I first studied its architecture and then read the code in depth. The bug emerged during that review.
>
> Regarding a trigger scenario (PoC – Proof of Concept): unfortunately, I don't have one. My system does not support io_uring (it returns ENOSYS, likely due to enterprise compatibility settings), so I couldn't run the liburing test suite. However, the fix itself is straightforward and the logic is clear.
That's not how any of this works, please always test your changes. If
you can't even build/boot them, don't expect others to do it for you.
thanks,
greg k-h
next prev parent reply other threads:[~2026-06-20 6:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-20 6:13 [BUG] io_uring: possible CQE32 overflow flush inconsistency in __io_cqring_overflow_flush() Cyber_black
2026-06-20 6:17 ` gregkh [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-19 8:05 Cyber_black
2026-06-19 16:07 ` Gabriel Krisman Bertazi
2026-06-19 4:49 Cyber_black
2026-06-19 6:00 ` Greg KH
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=2026062012-iphone-chasing-61e7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Cyberblackk@proton.me \
--cc=axboe@kernel.dk \
--cc=gabriel@krisman.be \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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