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.
Published: 2026-08-15
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Linux kernel’s i_ipmi_request() function contains a reference‑count leak when callers provide a supplied_recv message. The function unnecessarily increments the user’s nr_msgs reference and, on an error, fails to decrement it, resulting in a permanent leak that can consume kernel memory over time. This flaw does not allow immediate remote code execution but can lead to a denial‑of‑service condition if an attacker repeatedly triggers the vulnerable path, exhausting available resources. The weakness is a classic resource‑leak vulnerability, classified under CWE-401.

Affected Systems

Linux kernels running before the patch that introduces the explicit decrement in the error cleanup path are affected. All distributions that ship the kernel with i_ipmi_request() in its original form—prior to the commit linked in the advisory—are vulnerable; no version numbers are specified in the advisory, so the issue may exist across all recent kernel releases that have not applied the fix.

Risk and Exploitability

The CVSS score of 5.5 and the EPSS score of <1% suggest a moderate severity with low exploitation probability, but the exact exploitation likelihood remains unclear. The vulnerability is not listed in CISA’s KEV catalog. The attack vector is inferred to be local, requiring an attacker with access to execute IPMI requests that trigger the function. Repeated exploitation could exhaust kernel memory and cause system instability. Because no publicly available exploitation evidence exists, the overall risk cannot be precisely quantified.

Generated by OpenCVE AI on August 18, 2026 at 02:06 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the fix referenced in the advisory (commit 0fd23994 etc.).
  • Configure the system to disable or restrict IPMI functionality if the kernel cannot be updated immediately, ensuring that no external entity can trigger i_ipmi_request().
  • Verify that any custom or third‑party kernel modules interacting with IPMI also handle supplied_recv messages safely to prevent accidental reference count leaks.

Generated by OpenCVE AI on August 18, 2026 at 02:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4745-1 linux-6.12 security update
History

Sun, 23 Aug 2026 13:15:00 +0000


Tue, 18 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-911
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low


Sat, 15 Aug 2026 21:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-401

Sat, 15 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
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.
Title ipmi: fix refcount leak in i_ipmi_request()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-23T12:46:30.954Z

Reserved: 2026-08-09T03:40:39.901Z

Link: CVE-2026-72040

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:21:13.123

Modified: 2026-08-23T13:16:37.900

Link: CVE-2026-72040

cve-icon Redhat

Severity : Low

Publid Date: 2026-08-15T00:00:00Z

Links: CVE-2026-72040 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T02:15:04Z

Weaknesses
  • CWE-401

    Missing Release of Memory after Effective Lifetime

  • CWE-911

    Improper Update of Reference Count