ipmi: fix refcount leak in i_ipmi_request()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b52da4054ee0bf9ecb44996f2c83236ff50b3812 · < a3f3859cecacb64f18fd446271ece9a3b3f2d4de| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ipmi: fix refcount leak in i_ipmi_request()
When a caller provides a `supplied_recv` message to i_ipmi_request(), the function increments the user's `nr_msgs` reference count. If an error occurs later, the out_err cleanup path only frees the recv_msg if the function allocated it itself (i.e., !supplied_recv). In the supplied_recv case the cleanup is skipped, leaving the reference count elevated. The caller ipmi_request_supply_msgs() does not release the supplied_recv on error, so the reference is permanently leaked.
Fix this by explicitly reverting the reference count operations when a supplied recv_msg with a valid user pointer is present in the error path: decrement nr_msgs and drop the user's kref.
From the CVE record · Linux
The Linux kernel's IPMI request handler can permanently leak a user reference count when a caller supplies a receive message and a later error occurs. The input does not specify how an attacker could trigger this condition or whether it requires network access, authentication, or user interaction.
Engineers running the Linux kernel should check for this IPMI issue; affected versions are not specified.