Answer in brief
CVE-2026-72042 records a High severity (CVSS 7.8) vulnerability in ipmi: Fix user refcount underflow in event delivery. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b52da4054ee0bf9ecb44996f2c83236ff50b3812 <ddbb6e3dc9bb4743de686aa1598c31e745cee76b || >=b52da4054ee0bf9ecb44996f2c83236ff50b3812 <7be349d4fcc5e065295b83418a22d27a68afbdb6 || >=b52da4054ee0bf9ecb44996f2c83236ff50b3812 <6aa9e61c46465d231e9beddf56af7effd71be682 || f63723ca7d7623f9dae1990973cd158671f03c56 || 348121b29594d42d1635648fd3ed31dfa25351d5 || 53d6e403affbf6df2c859a0ea00ccfc1e72090ca || 0ed73be9a2547ffb9b5c1d879ad9bfab73d920b5 || >=6.1.157 <6.2 || >=6.6.113 <6.7 || >=6.12.54 <6.13 || >=6.17.4 <6.18 | ddbb6e3dc9bb4743de686aa1598c31e745cee76b, 7be349d4fcc5e065295b83418a22d27a68afbdb6, 6aa9e61c46465d231e9beddf56af7effd71be682, 6.2, 6.7, 6.13, 6.18 |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.