3846 matches found
CVE-2026-74334
The CVE-2026-74334 issue affects the Linux kernel RDMA/nldev path, where locking around mr->pd was unsafe because pd became variable under rereg_mr and touches could race. The fix uses mr->device instead of mr->pd->device and introduces an rdma_restrack_sync() operation to ensure stal...
CVE-2026-74334 RDMA/nldev: Fix locking when accessing mr->pd
In the Linux kernel, the following vulnerability has been resolved: RDMA/nldev: Fix locking when accessing mr-pd Sashiko points out that, due to reregmr, the PD is actually variable and all the touches in nldev are racy. Use mr-device instead of mr-pd-device. Getting the PD restrack ID is more...
CVE-2026-74334 RDMA/nldev: Fix locking when accessing mr->pd
In the Linux kernel, the following vulnerability has been resolved: RDMA/nldev: Fix locking when accessing mr-pd Sashiko points out that, due to reregmr, the PD is actually variable and all the touches in nldev are racy. Use mr-device instead of mr-pd-device. Getting the PD restrack ID is more...
EUVD-2026-59445
In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix FRMR set pinned push error path Add destruction of FRMR handles in case the push to the pool fails. This prevents resources leak in case pool page allocation fails...
CVE-2026-74298 RDMA/core: Fix FRMR set pinned push error path
In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix FRMR set pinned push error path Add destruction of FRMR handles in case the push to the pool fails. This prevents resources leak in case pool page allocation fails...
CVE-2026-74298
CVE-2026-74298 pertains to the Linux kernel, specifically the RDMA/core path. The vulnerability is resolved by fixing the FRMR set pinned push error path and by adding destruction of FRMR handles when pushing to the pool fails, preventing resource leaks if pool page allocation fails. Documents do...
CVE-2026-74299
CVE-2026-74299 affects the Linux kernel RDMA/core subsystem. A FRMR aging path could leak an mkey when aging pinned-handle pools move handles between active/inactive queues and a new page allocation fails. The fix adds push_queue_to_queue_locked() to populate the destination tail from the source ...
CVE-2026-74299 RDMA/core: Fix FRMR aging push to queue error flow
In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix FRMR aging push to queue error flow Aging pools with pinned handles requires moving handles from the active queue to a non-empty inactive queue that might fail on new page allocation, we are currently not handling...
CVE-2026-74299 RDMA/core: Fix FRMR aging push to queue error flow
In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix FRMR aging push to queue error flow Aging pools with pinned handles requires moving handles from the active queue to a non-empty inactive queue that might fail on new page allocation, we are currently not handling...
CVE-2026-74298 RDMA/core: Fix FRMR set pinned push error path
In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix FRMR set pinned push error path Add destruction of FRMR handles in case the push to the pool fails. This prevents resources leak in case pool page allocation fails...
EUVD-2026-59446
In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix FRMR aging push to queue error flow Aging pools with pinned handles requires moving handles from the active queue to a non-empty inactive queue that might fail on new page allocation, we are currently not handling...
EUVD-2026-59444
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix undefined shift of user RQ WQE size setrqsize computes the RQ WQE size as "1 rqwqeshift" based on the user-provided rqwqeshift, which is only checked to be greater than 32, so shifts of 32 are still accepted. A shi...
CVE-2026-74297
The CVE-2026-74297 entry details a Linux kernel vulnerability in the RDMA/mlx5 path relating to RQ WQE size calculation. The flaw arises in set_rq_size(), which computes the RQ WQE size as 1 < 32; shifts of 32 are accepted and a shift of 31 can overflow a signed integer, causing undefined beha...
CVE-2026-74297 RDMA/mlx5: Fix undefined shift of user RQ WQE size
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix undefined shift of user RQ WQE size setrqsize computes the RQ WQE size as "1 rqwqeshift" based on the user-provided rqwqeshift, which is only checked to be greater than 32, so shifts of 32 are still accepted. A shi...
CVE-2026-74297 RDMA/mlx5: Fix undefined shift of user RQ WQE size
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix undefined shift of user RQ WQE size setrqsize computes the RQ WQE size as "1 rqwqeshift" based on the user-provided rqwqeshift, which is only checked to be greater than 32, so shifts of 32 are still accepted. A shi...
EUVD-2026-59443
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Release the HW‑provided UAR index rather than the SW one Free the UAR index returned by the hardware...
CVE-2026-74296 RDMA/mlx5: Release the HW‑provided UAR index rather than the SW one
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Release the HW‑provided UAR index rather than the SW one Free the UAR index returned by the hardware...
CVE-2026-74296 RDMA/mlx5: Release the HW‑provided UAR index rather than the SW one
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Release the HW‑provided UAR index rather than the SW one Free the UAR index returned by the hardware...
CVE-2026-74296
CVE-2026-74296 – Linux kernel RDMA/mlx5 UAR index handling : The affected component is the Linux kernel with the RDMA/mlx5 driver. The described issue is a change in resource management: freeing the UAR index that is provided by hardware rather than the software-supplied index. The impact is reco...
CVE-2026-72501 RDMA/bnxt_re: Initialize dpi variable to zero
In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxtre: Initialize dpi variable to zero dpi is initialized only for BNXTREALLOCWCPAGE, but copied for all the cases. So initialize the dpi to 0...