<?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 14:56:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-63955 — mm/vmalloc: do not trigger BUG() on BH disabled context</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-63955</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;mm/vmalloc: do not trigger BUG() on BH disabled context&lt;/p&gt;
&lt;p&gt;__get_vm_area_node() currently triggers a BUG() if in_interrupt() returns
true.  However, in_interrupt() also reports true when BH are disabled.&lt;/p&gt;
&lt;p&gt;The bridge code can call rhashtable_lookup_insert_fast() with bottom
halves disabled:&lt;/p&gt;
&lt;p&gt;__vlan_add()
 -&amp;gt; br_fdb_add_local()
  spin_lock_bh(&amp;amp;br-&amp;gt;hash_lock); &amp;lt;-- Disable BH
   -&amp;gt; fdb_add_local()
    -&amp;gt; fdb_create()
     -&amp;gt; rhashtable_lookup_insert_fast()
      -&amp;gt; kvmalloc()
       -&amp;gt; vmalloc()
        -&amp;gt; __get_vm_area_node()
         -&amp;gt; BUG_ON(in_interrupt())
  spin_unlock_bh(&amp;amp;br-&amp;gt;hash_lock)&lt;/p&gt;
&lt;p&gt;this triggers the BUG() despite the caller not being in NMI or
hard IRQ context.&lt;/p&gt;
&lt;p&gt;Replace the in_interrupt() check with in_nmi() || in_hardirq().&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;mm/vmalloc: do not trigger BUG() on BH disabled context&lt;/p&gt;
&lt;p&gt;__get_vm_area_node() currently triggers a BUG() if in_interrupt() returns
true.  However, in_interrupt() also reports true when BH are disabled.&lt;/p&gt;
&lt;p&gt;The bridge code can call rhashtable_lookup_insert_fast() with bottom
halves disabled:&lt;/p&gt;
&lt;p&gt;__vlan_add()
 -&amp;gt; br_fdb_add_local()
  spin_lock_bh(&amp;amp;br-&amp;gt;hash_lock); &amp;lt;-- Disable BH
   -&amp;gt; fdb_add_local()
    -&amp;gt; fdb_create()
     -&amp;gt; rhashtable_lookup_insert_fast()
      -&amp;gt; kvmalloc()
       -&amp;gt; vmalloc()
        -&amp;gt; __get_vm_area_node()
         -&amp;gt; BUG_ON(in_interrupt())
  spin_unlock_bh(&amp;amp;br-&amp;gt;hash_lock)&lt;/p&gt;
&lt;p&gt;this triggers the BUG() despite the caller not being in NMI or
hard IRQ context.&lt;/p&gt;
&lt;p&gt;Replace the in_interrupt() check with in_nmi() || in_hardirq().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-63955</guid>
    </item>
  </channel>
</rss>
