diff options
| author | Jason Gunthorpe <jgg@nvidia.com> | 2026-07-02 13:47:10 -0300 |
|---|---|---|
| committer | Jason Gunthorpe <jgg@nvidia.com> | 2026-07-02 13:47:10 -0300 |
| commit | 011199f46f44a9fd93a9e5ab5d7fd1328d80e9bf (patch) | |
| tree | 2c30b23d5a5cacc5bd5ec2c6105fcd1cdfe17271 /kernel/locking/lock_events.c | |
| parent | 5911f6d6e7cce5f35bcaabc1895616e10a6d0aa2 (diff) | |
| download | linux-next-011199f46f44a9fd93a9e5ab5d7fd1328d80e9bf.tar.gz linux-next-011199f46f44a9fd93a9e5ab5d7fd1328d80e9bf.zip | |
RDMA/uverbs: Add UVERBS_ATTR_UHW to UVERBS_METHOD_REG_MR
The original commit missed that three drivers (mthca, irdma, siw) have UHW
data associated with reg_mr that cannot be passed through the ioctl. They
also assume that the udata cannot be NULL, so failing to pass a valid
udata can trigger a NULL udata crash in those drivers.
This never happens in real systems since in rdma-core ibv_cmd_reg_mr_ex()
does not accept a udata and those three drivers don't use it, however a
malicious userspace could trigger it.
Cc: stable@vger.kernel.org
Fixes: 5b2e45049dc0 ("IB/core: Add UVERBS_METHOD_REG_MR on the MR object")
Reported-by: Jacob Moroni <jmoroni@google.com>
Closes: https://lore.kernel.org/all/CAHYDg1TOGxRGZrS69d4Y--Shj_DZv0nJuM73iHUBwBM70g_t3Q@mail.gmail.com
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Diffstat (limited to 'kernel/locking/lock_events.c')
0 files changed, 0 insertions, 0 deletions