In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix integer overflow…

Why it is Red

• CVSS 9.8 critical
• Remotely exploitable without logging in
• On your watchlist: linux kernel

References

• https://git.kernel.org/stable/c/2f3b705144e3a3c14184fec6e354680081fe91ec
• https://git.kernel.org/stable/c/3431f525718f6b07da308cda6d44f8cb548bbd37
• https://git.kernel.org/stable/c/5d9426a74fc8cb8f375fcdc19b465a030f9b8cab
• https://git.kernel.org/stable/c/b7d2118660545a00b21e83010ded1a231c6fb8c5
• https://git.kernel.org/stable/c/d10e2a08799e858d3e71ea4169bcd018f216d444

Original description

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix integer overflow in mr_check_range() leading to OOB access mr_check_range() validates that [iova, iova+length) falls within the registered MR range using wraparound-prone arithmetic: if (iova < mr->ibmr.iova || iova + length > mr->ibmr.iova + mr->ibmr.length) A remote peer can craft an RDMA-Write/Read RETH so that iova + length wraps to 0 (e.g. iova=0xfffffffffffffff8, length=8), bypassing the check. rxe_mr_iova_to_index() then computes a huge index (int idx, only guarded by WARN_ON) and rxe_mr_copy_xarray() dereferences mr->page_info[huge], causing an out-of-bounds read/write and a kernel oops that is triggerable by an unauthenticated remote peer. Rewrite the check in overflow-safe form; the first two clauses guarantee that the subsequent subtractions do not underflow: if (iova < mr->ibmr.iova || length > mr->ibmr.length || iova - mr->ibmr.iova > mr->ibmr.length - length) With the fix, mr_check_range() returns -EINVAL for the crafted iova and the responder reports REMOTE_ACCESS_ERROR instead of triggering the OOB.