CVE-2026-72040 — ipmi: fix refcount leak in i_ipmi_request()
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ f63723ca7d7623f9dae1990973cd158671f03c56 and < 122ca6b2af714e114c9b872a48372ace31a9ab1f≥ 348121b29594d42d1635648fd3ed31dfa25351d5 and < 9409e18ffe7378d202efe1cf69989df9f67b0369≥ 53d6e403affbf6df2c859a0ea00ccfc1e72090ca and < e2a3b77df6aef031455dd83ea8ed4344b7dca1f9≥ b52da4054ee0bf9ecb44996f2c83236ff50b3812 and < f5c5065963024390ddad51bd455d1adc710de575≥ b52da4054ee0bf9ecb44996f2c83236ff50b3812 and < 0fd23994ec8c5436d9f0b50848deb87ed933e6b3≥ b52da4054ee0bf9ecb44996f2c83236ff50b3812 and < a3f3859cecacb64f18fd446271ece9a3b3f2d4deversion 0ed73be9a2547ffb9b5c1d879ad9bfab73d920b5≥ 6.1.157 and < 6.1.184 and 4 more≥ 6.6.113 and < 6.6.148≥ 6.12.54 and < 6.12.101≥ 6.17.4 and < 6.18version 6.18 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 30, 2026 · 15 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
6 on the record
- git.kernel.org/stable/c/122ca6b2af714e114c9b872a48372ace31a9ab1f
- git.kernel.org/stable/c/9409e18ffe7378d202efe1cf69989df9f67b0369
- git.kernel.org/stable/c/e2a3b77df6aef031455dd83ea8ed4344b7dca1f9
- git.kernel.org/stable/c/f5c5065963024390ddad51bd455d1adc710de575
- git.kernel.org/stable/c/0fd23994ec8c5436d9f0b50848deb87ed933e6b3
- git.kernel.org/stable/c/a3f3859cecacb64f18fd446271ece9a3b3f2d4de
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-72040 is "ipmi: fix refcount leak in i_ipmi_request()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.