Public vulnerability disclosure

CVE-2026-72040

ipmi: fix refcount leak in i_ipmi_request()

published

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.

Technical severityUnscoredNo score in collected sources
Published2026-08-15Source updated 2026-11-06
Collected2026-11-062 attributed sources

Fixes and workarounds

No remediation reported in collected sources.

Missing remediation information is not evidence that no patch exists.

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Linux
Linux
≥ f63723ca7d7623f9dae1990973cd158671f03c56; < 122ca6b2af714e114c9b872a48372ace31a9ab1f (affected, git)
≥ 348121b29594d42d1635648fd3ed31dfa25351d5; < 9409e18ffe7378d202efe1cf69989df9f67b0369 (affected, git)
≥ 53d6e403affbf6df2c859a0ea00ccfc1e72090ca; < e2a3b77df6aef031455dd83ea8ed4344b7dca1f9 (affected, git)
≥ b52da4054ee0bf9ecb44996f2c83236ff50b3812; < f5c5065963024390ddad51bd455d1adc710de575 (affected, git)
≥ b52da4054ee0bf9ecb44996f2c83236ff50b3812; < 0fd23994ec8c5436d9f0b50848deb87ed933e6b3 (affected, git)
≥ b52da4054ee0bf9ecb44996f2c83236ff50b3812; < a3f3859cecacb64f18fd446271ece9a3b3f2d4de (affected, git)
0ed73be9a2547ffb9b5c1d879ad9bfab73d920b5 (affected, git)
≥ 6.1.157; < 6.1.184 (affected, semver)
≥ 6.6.113; < 6.6.148 (affected, semver)
≥ 6.12.54; < 6.12.101 (affected, semver)
≥ 6.17.4; < 6.18 (affected, semver)
Other versions: unaffected
CNA: Linux
Linux
Linux
6.18 (affected)
≥ 0; < 6.18 (unaffected, semver)
≥ 6.1.184; ≤ 6.1.* (unaffected, semver)
≥ 6.6.148; ≤ 6.6.* (unaffected, semver)
≥ 6.12.101; ≤ 6.12.* (unaffected, semver)
≥ 6.18.40; ≤ 6.18.* (unaffected, semver)
≥ 7.1.5; ≤ 7.1.* (unaffected, semver)
≥ 7.2; ≤ * (unaffected, original_commit_for_fix)
Other versions: affected
CNA: Linux

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

No CVSS assessment reported. An unscored record is not a low-severity determination.

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide