<?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>Sun, 04 Oct 2026 02:49:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-46177 — ipmi: Add limits to event and receive message requests</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-46177</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: Add limits to event and receive message requests&lt;/p&gt;
&lt;p&gt;The driver would just fetch events and receive messages until the
BMC said it was done.  To avoid issues with BMCs that never say they are
done, add a limit of 10 fetches at a time.&lt;/p&gt;
&lt;p&gt;In addition, an si interface has an attn state it can return from the
hardware which is supposed to cause a flag fetch to see if the driver
needs to fetch events or message or a few other things.  If the attn
bit gets stuck, it&amp;#39;s a similar problem.  So allow messages in between
flag fetches so the driver itself doesn&amp;#39;t get stuck.&lt;/p&gt;
&lt;p&gt;This is a more general fix than the previous fix for the specific bad
BMC, but should fix the more general issue of a BMC that won&amp;#39;t stop
saying it has data.&lt;/p&gt;
&lt;p&gt;This has been there from the beginning of the driver.  It&amp;#39;s not a bug
per-se, but it is accounting for bugs in BMCs.&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: Add limits to event and receive message requests&lt;/p&gt;
&lt;p&gt;The driver would just fetch events and receive messages until the
BMC said it was done.  To avoid issues with BMCs that never say they are
done, add a limit of 10 fetches at a time.&lt;/p&gt;
&lt;p&gt;In addition, an si interface has an attn state it can return from the
hardware which is supposed to cause a flag fetch to see if the driver
needs to fetch events or message or a few other things.  If the attn
bit gets stuck, it&amp;#39;s a similar problem.  So allow messages in between
flag fetches so the driver itself doesn&amp;#39;t get stuck.&lt;/p&gt;
&lt;p&gt;This is a more general fix than the previous fix for the specific bad
BMC, but should fix the more general issue of a BMC that won&amp;#39;t stop
saying it has data.&lt;/p&gt;
&lt;p&gt;This has been there from the beginning of the driver.  It&amp;#39;s not a bug
per-se, but it is accounting for bugs in BMCs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-46177</guid>
    </item>
  </channel>
</rss>
