From: Jens Axboe <axboe@kernel.dk>
To: Andres Berbescu <aberbescu@gmail.com>
Cc: io-uring@vger.kernel.org, sashal@kernel.org,
gregkh@linuxfoundation.org, security@kernel.org
Subject: Re: [SECURITY] io_uring: provided-buffer ownership loss across MSG_WAITALL retry
Date: Wed, 16 Sep 2026 22:22:49 -0600 [thread overview]
Message-ID: <f430d1ce-4803-4bfd-b6ba-2065c84d03f5@kernel.dk> (raw)
In-Reply-To: <CAAOipkaT5tDsf-FtP0hC0iUG2fEe0PowqeQfV4m-cuooJeZX2w@mail.gmail.com>
On 9/16/26 3:35 PM, Andres Berbescu wrote:
> Hello,
>
> I am reporting one io_uring provided-buffer ownership/accounting bug
> with two MSG_WAITALL manifestations: bundle-tail reuse and
> incremental-buffer reuse. The two cases violate the same invariant and
> should be handled as one report.
For the three you sent:
1) No point CC'ing security@ when you're sending it to a public list as
well.
2) Send a patch
3) Potential data corruption is a not a security issue in the first
place.
Everybody has an LLM these days, if you have it find issues or potential
issues in kernel code, have it generate a patch as well and send it
along. The documentation is pretty clear on that. That's more useful
that 20kb+ of drivel report.
--
Jens Axboe
prev parent reply other threads:[~2026-09-17 4:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 21:35 [SECURITY] io_uring: provided-buffer ownership loss across MSG_WAITALL retry Andres Berbescu
2026-09-17 4:22 ` Jens Axboe [this message]
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=f430d1ce-4803-4bfd-b6ba-2065c84d03f5@kernel.dk \
--to=axboe@kernel.dk \
--cc=aberbescu@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=io-uring@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=security@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.