linux-kernel - Re: [PATCH] io_uring/kbuf: use READ_ONCE() for userspace-mapped memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <176488843155.1025927.15790018424964919710.b4-ty@kernel.dk>
Date: Thu, 04 Dec 2025 15:47:11 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Caleb Sander Mateos <csander@...estorage.com>
Cc: Joanne Koong <joannelkoong@...il.com>, io-uring@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] io_uring/kbuf: use READ_ONCE() for userspace-mapped
 memory


On Thu, 04 Dec 2025 15:43:31 -0700, Caleb Sander Mateos wrote:
> The struct io_uring_buf elements in a buffer ring are in a memory region
> accessible from userspace. A malicious/buggy userspace program could
> therefore write to them at any time, so they should be accessed with
> READ_ONCE() in the kernel. Commit 98b6fa62c84f ("io_uring/kbuf: always
> use READ_ONCE() to read ring provided buffer lengths") already switched
> the reads of the len field to READ_ONCE(). Do the same for bid and addr.
> 
> [...]

Applied, thanks!

[1/1] io_uring/kbuf: use READ_ONCE() for userspace-mapped memory
      commit: 78385c7299f7514697d196b3233a91bd5e485591

Best regards,
-- 
Jens Axboe