<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 15:25:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72042 — ipmi: Fix user refcount underflow in event delivery</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72042</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipmi: Fix user refcount underflow in event delivery&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;That rollback path still drops user-&amp;gt;refcount explicitly after freeing each
message. The extra put can free a user that remains linked on intf-&amp;gt;users,
so later event delivery may dereference a freed user or trip refcount_t&amp;#39;s
addition-on-zero warning when ipmi_alloc_recv_msg() tries to acquire
another reference.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipmi: Fix user refcount underflow in event delivery&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;That rollback path still drops user-&amp;gt;refcount explicitly after freeing each
message. The extra put can free a user that remains linked on intf-&amp;gt;users,
so later event delivery may dereference a freed user or trip refcount_t&amp;#39;s
addition-on-zero warning when ipmi_alloc_recv_msg() tries to acquire
another reference.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72042</guid>
    </item>
  </channel>
</rss>
