Answer in brief
CVE-2026-72040 records a Unknown severity vulnerability in ipmi: fix refcount leak in i_ipmi_request(). 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.
A CVSS score is not reported in the current record. 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 | >=348121b29594d42d1635648fd3ed31dfa25351d5 <9409e18ffe7378d202efe1cf69989df9f67b0369 || >=53d6e403affbf6df2c859a0ea00ccfc1e72090ca <e2a3b77df6aef031455dd83ea8ed4344b7dca1f9 || >=b52da4054ee0bf9ecb44996f2c83236ff50b3812 <f5c5065963024390ddad51bd455d1adc710de575 || >=b52da4054ee0bf9ecb44996f2c83236ff50b3812 <0fd23994ec8c5436d9f0b50848deb87ed933e6b3 || >=b52da4054ee0bf9ecb44996f2c83236ff50b3812 <a3f3859cecacb64f18fd446271ece9a3b3f2d4de || f63723ca7d7623f9dae1990973cd158671f03c56 || 0ed73be9a2547ffb9b5c1d879ad9bfab73d920b5 || >=6.6.113 <6.6.148 || >=6.12.54 <6.12.101 || >=6.1.157 <6.2 || >=6.17.4 <6.18 | 9409e18ffe7378d202efe1cf69989df9f67b0369, e2a3b77df6aef031455dd83ea8ed4344b7dca1f9, f5c5065963024390ddad51bd455d1adc710de575, 0fd23994ec8c5436d9f0b50848deb87ed933e6b3, a3f3859cecacb64f18fd446271ece9a3b3f2d4de, 6.6.148, 6.12.101, 6.2, 6.18 |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 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 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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72040 records a Unknown severity vulnerability in ipmi: fix refcount leak in i_ipmi_request(). 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.
A CVSS score is not reported in the current record. 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 | >=348121b29594d42d1635648fd3ed31dfa25351d5 <9409e18ffe7378d202efe1cf69989df9f67b0369 || >=53d6e403affbf6df2c859a0ea00ccfc1e72090ca <e2a3b77df6aef031455dd83ea8ed4344b7dca1f9 || >=b52da4054ee0bf9ecb44996f2c83236ff50b3812 <f5c5065963024390ddad51bd455d1adc710de575 || >=b52da4054ee0bf9ecb44996f2c83236ff50b3812 <0fd23994ec8c5436d9f0b50848deb87ed933e6b3 || >=b52da4054ee0bf9ecb44996f2c83236ff50b3812 <a3f3859cecacb64f18fd446271ece9a3b3f2d4de || f63723ca7d7623f9dae1990973cd158671f03c56 || 0ed73be9a2547ffb9b5c1d879ad9bfab73d920b5 || >=6.6.113 <6.6.148 || >=6.12.54 <6.12.101 || >=6.1.157 <6.2 || >=6.17.4 <6.18 | 9409e18ffe7378d202efe1cf69989df9f67b0369, e2a3b77df6aef031455dd83ea8ed4344b7dca1f9, f5c5065963024390ddad51bd455d1adc710de575, 0fd23994ec8c5436d9f0b50848deb87ed933e6b3, a3f3859cecacb64f18fd446271ece9a3b3f2d4de, 6.6.148, 6.12.101, 6.2, 6.18 |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 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 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.
Quoted source text, attributed separately from HOL analysis.