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-72042ipmi: Fix user refcount underflow in event delivery

Description

In the Linux kernel, the following vulnerability has been resolved: ipmi: Fix user refcount underflow in event delivery ipmi_alloc_recv_msg(user) takes the temporary user reference owned by the receive message, and ipmi_free_recv_msg() drops it again. If event delivery fails after allocating receive messages for earlier users, handle_read_event_rsp() rolls those messages back with ipmi_free_recv_msg(). That rollback path still drops user->refcount explicitly after freeing each message. The extra put can free a user that remains linked on intf->users, so later event delivery may dereference a freed user or trip refcount_t's addition-on-zero warning when ipmi_alloc_recv_msg() tries to acquire another reference. Remove the stale explicit put and the now-dead user assignment. Keep the list_del() and ipmi_free_recv_msg() calls; they are the required rollback operations.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 days 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

CVSS scores of CVE-2026-72042, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (14 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected b52da4054ee0bf9ecb44996f2c83236ff50b3812 – < ddbb6e3dc9bb4743de686aa1598c31e745cee76b
    • affected b52da4054ee0bf9ecb44996f2c83236ff50b3812 – < 7be349d4fcc5e065295b83418a22d27a68afbdb6
    • affected b52da4054ee0bf9ecb44996f2c83236ff50b3812 – < 6aa9e61c46465d231e9beddf56af7effd71be682
    • affected f63723ca7d7623f9dae1990973cd158671f03c56
    • affected 348121b29594d42d1635648fd3ed31dfa25351d5
    • affected 53d6e403affbf6df2c859a0ea00ccfc1e72090ca
    • affected 0ed73be9a2547ffb9b5c1d879ad9bfab73d920b5
    • affected 6.1.157 – < 6.2
    • affected 6.6.113 – < 6.7
    • affected 6.12.54 – < 6.13
    • affected 6.17.4 – < 6.18
  • Linux · Linux

    • affected 6.18
    • unaffected < 6.18
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References3

Sources

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

Badge for a README or a ticket

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

Record last updated .