CVE-2026-72040

ipmi: fix refcount leak in i_ipmi_request()

N/A
Published: August 15, 2026 at 05:51 AM UTC
Updated: August 23, 2026 at 01:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 6.17.46.1.157 ≤ v < 6.1.1846.12.54 ≤ v < 6.12.1016.17.4 ≤ v < 6.186.18 ≤ v < 6.18.406.18 ≤ v < 7.1.56.18 ≤ v < 7.26.6.113 ≤ v < 6.6.1480ed73be9a2547ffb9b5c1d879ad9bfab73d920b5348121b29594d42d1635648fd3ed31dfa25351d553d6e403affbf6df2c859a0ea00ccfc1e72090ca6.1.1576.12.546.17.46.186.6.113b52da4054ee0bf9ecb44996f2c83236ff50b3812f63723ca7d7623f9dae1990973cd158671f03c56
Vendor states this is fixed in 0fd23994ec8c5436d9f0b50848deb87ed933e6b3 (fixed)
Vendor states this is fixed in 122ca6b2af714e114c9b872a48372ace31a9ab1f (fixed)
Vendor states this is fixed in 9409e18ffe7378d202efe1cf69989df9f67b0369 (fixed)
Vendor states this is fixed in a3f3859cecacb64f18fd446271ece9a3b3f2d4de (fixed)
Vendor states this is fixed in e2a3b77df6aef031455dd83ea8ed4344b7dca1f9 (fixed)
Vendor states this is fixed in f5c5065963024390ddad51bd455d1adc710de575 (fixed)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card