Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 3 weeks, 3 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
ipmi: Fix user refcount underflow in event delivery

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.

Affected products

Linux
  • <6.18
  • <6aa9e61c46465d231e9beddf56af7effd71be682
  • ==0ed73be9a2547ffb9b5c1d879ad9bfab73d920b5
  • <6.2
  • <6.7
  • <6.13
  • <6.18
  • =<*
  • ==6.18
  • =<6.18.*
  • ==348121b29594d42d1635648fd3ed31dfa25351d5
  • <ddbb6e3dc9bb4743de686aa1598c31e745cee76b
  • <7be349d4fcc5e065295b83418a22d27a68afbdb6
  • ==53d6e403affbf6df2c859a0ea00ccfc1e72090ca
  • =<7.1.*
  • ==f63723ca7d7623f9dae1990973cd158671f03c56