RDMA/uverbs: Guard legacy bundles without method_elm
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/uverbs: Guard legacy bundles without method_elm
The legacy write() path dispatches through a uverbs_api_write_method, but the uverbs_attr_bundle passed to provider code does not have an ioctl method element. If malformed provider input causes the common uverbs validation code to emit an error message, uverbs_get_handler_fn() dereferences the uninitialized method_elm pointer.
Initialize method_elm explicitly for legacy bundles and make uverbs_get_handler_fn() return NULL when no ioctl method is present. The legacy dispatcher continues to use its local write method, while the ioctl path continues to use the registered ioctl handler.
From the CVE record · Linux
The Linux kernel’s RDMA/uverbs legacy write path passes provider code an attribute bundle without an initialized ioctl method element. If malformed provider input causes validation to emit an error, uverbs_get_handler_fn() dereferences that uninitialized pointer. The input does not specify authentication or user-interaction requirements.
Engineers running the Linux kernel should check whether their builds include the affected RDMA/uverbs code; affected versions were not provided.