linux-kernel - [PATCH 0/4] io_uring: verify that reserved fields are 0

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-next>] [day] [month] [year] [list]

Date:   Tue, 12 Apr 2022 09:30:38 -0700
From:   Dylan Yudaken <dylany@...com>
To:     <io-uring@...r.kernel.org>
CC:     <axboe@...nel.dk>, <asml.silence@...il.com>,
        <linux-kernel@...r.kernel.org>, <kernel-team@...com>,
        Dylan Yudaken <dylany@...com>
Subject: [PATCH 0/4] io_uring: verify that reserved fields are 0

A few reserved fields are not verified to be 0. In preparation for possibly using these fields later we should verify that they are passed as 0.

One extra field I do not have confidence in verifying is up.nr in io_register_files_update(). Should this also be checked to be zero?

Patch 1 in this series just moves a validation out of __io_register_rsrc_update as it was duplicated
Patch 2-4 add verifications for reserved fields

Dylan Yudaken (4):
  io_uring: move io_uring_rsrc_update2 validation
  io_uring: verify that resv2 is 0 in io_uring_rsrc_update2
  io_uring: verify resv is 0 in ringfd register/unregister
  io_uring: verify pad field is 0 in io_get_ext_arg

 fs/io_uring.c | 16 ++++++++++++----
 1 file changed, 12 insertions(+), 4 deletions(-)


base-commit: 0f8da75b51ac863b9435368bd50691718cc454b0
-- 
2.30.2