ipmi: Fix user refcount underflow in event delivery
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ipmi: Fix user refcount underflow in event delivery
ipmi_alloc_recv_msg(user) takes the temporary user reference owned by the receive message, and ipmi_free_recv_msg() drops it again. If event delivery fails after allocating receive messages for earlier users, handle_read_event_rsp() rolls those messages back with ipmi_free_recv_msg().
That rollback path still drops user->refcount explicitly after freeing each message. The extra put can free a user that remains linked on intf->users, so later event delivery may dereference a freed user or trip refcount_t's addition-on-zero warning when ipmi_alloc_recv_msg() tries to acquire another reference.
Remove the stale explicit put and the now-dead user assignment. Keep the list_del() and ipmi_free_recv_msg() calls; they are the required rollback operations.
From the CVE record · Linux
The Linux kernel IPMI event-delivery rollback path can drop a user reference twice when delivery fails after receive messages have been allocated for earlier users. This can free a user still on the interface’s user list, allowing later event delivery to dereference freed memory or trigger a refcount warning. The input does not specify how an attacker could trigger the failure or whether access or user interaction is required.
Engineers running Linux kernels with IPMI support should check their versions against the vendor advisory; affected versions are not specified.