RDMA/rxe: Fix the error "trying to register non-static key in rxe_cleanup_task"
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
RDMA/rxe: Fix the error "trying to register non-static key in rxe_cleanup_task"
In the function rxe_create_qp(), rxe_qp_from_init() is called to initialize qp, internally things like rxe_init_task are not setup until rxe_qp_init_req().
If an error occurred before this point then the unwind will call rxe_cleanup() and eventually to rxe_qp_do_cleanup()/rxe_cleanup_task() which will oops when trying to access the uninitialized spinlock.
If rxe_init_task is not executed, rxe_cleanup_task will not be called.
From the CVE record · Linux
The Linux kernel’s RDMA/rxe code can access an uninitialized spinlock during queue pair cleanup if initialization fails before the task is set up, causing a kernel oops. The input does not specify how an attacker could trigger the error or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with RDMA/rxe should check their exposure; affected versions are not specified.