Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-72040

ipmi: fix refcount leak in i_ipmi_request()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected f63723ca7d7623f9dae1990973cd158671f03c56 – < 122ca6b2af714e114c9b872a48372ace31a9ab1f
    • affected 348121b29594d42d1635648fd3ed31dfa25351d5 – < 9409e18ffe7378d202efe1cf69989df9f67b0369
    • affected 53d6e403affbf6df2c859a0ea00ccfc1e72090ca – < e2a3b77df6aef031455dd83ea8ed4344b7dca1f9
    • affected b52da4054ee0bf9ecb44996f2c83236ff50b3812 – < f5c5065963024390ddad51bd455d1adc710de575
    • affected b52da4054ee0bf9ecb44996f2c83236ff50b3812 – < 0fd23994ec8c5436d9f0b50848deb87ed933e6b3
    • affected b52da4054ee0bf9ecb44996f2c83236ff50b3812 – < a3f3859cecacb64f18fd446271ece9a3b3f2d4de
    • affected 0ed73be9a2547ffb9b5c1d879ad9bfab73d920b5
    • affected 6.1.157 – < 6.1.184
    • affected 6.6.113 – < 6.6.148
    • affected 6.12.54 – < 6.12.101
    • affected 6.17.4 – < 6.18
  • Linux · Linux

    • affected 6.18
    • unaffected < 6.18
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-72040 badge
[![CVE-2026-72040](https://cveledger.app/badge/CVE-2026-72040.svg)](https://cveledger.app/cve/CVE-2026-72040)

Record last updated .