<?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>Tue, 29 Sep 2026 08:43:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90082 — net: mana: Cap MSI-X vectors to the device MSI-X table size</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90082</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;net: mana: Cap MSI-X vectors to the device MSI-X table size&lt;/p&gt;
&lt;p&gt;mana_gd_query_max_resources() sizes gc-&amp;gt;num_msix_usable from resp.max_msix
and the CPU count, but never from the device MSI-X table. On a 1792 vCPU
M-series VM that yields 1793 while the table has 1024 entries, and
mana_gd_setup_remaining_irqs() then walks indices 1..1792, running off the
end of the region mapped by msix_map_region():&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ff8e347f8b99800c
  RIP: 0010:msix_prepare_msi_desc+0x7a/0x90
  RAX: 0000000000004000 RBX: ff4330cb164ea780 RCX: ff8e347f8b998000
  Call Trace:
   &amp;lt;TASK&amp;gt;
   __msi_domain_alloc_irqs+0x13a/0x440
   msi_domain_alloc_irq_at+0x149/0x1b0
   mana_gd_setup+0x351/0x890
   mana_gd_probe+0x274/0x390
   &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;RAX is index 1024 * PCI_MSIX_ENTRY_SIZE, one entry past the table.&lt;/p&gt;
&lt;p&gt;msi_insert_desc() does range check the index, but only against the MSI
domain hwsize, which matches the table only for devices on an MSI parent
domain. With a global PCI/MSI domain hwsize is MSI_XA_DOMAIN_SIZE, so
nothing bounds the request.&lt;/p&gt;
&lt;p&gt;Cap num_msix_usable with pci_msix_vec_count().&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;net: mana: Cap MSI-X vectors to the device MSI-X table size&lt;/p&gt;
&lt;p&gt;mana_gd_query_max_resources() sizes gc-&amp;gt;num_msix_usable from resp.max_msix
and the CPU count, but never from the device MSI-X table. On a 1792 vCPU
M-series VM that yields 1793 while the table has 1024 entries, and
mana_gd_setup_remaining_irqs() then walks indices 1..1792, running off the
end of the region mapped by msix_map_region():&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ff8e347f8b99800c
  RIP: 0010:msix_prepare_msi_desc+0x7a/0x90
  RAX: 0000000000004000 RBX: ff4330cb164ea780 RCX: ff8e347f8b998000
  Call Trace:
   &amp;lt;TASK&amp;gt;
   __msi_domain_alloc_irqs+0x13a/0x440
   msi_domain_alloc_irq_at+0x149/0x1b0
   mana_gd_setup+0x351/0x890
   mana_gd_probe+0x274/0x390
   &amp;lt;/TASK&amp;gt;&lt;/p&gt;
&lt;p&gt;RAX is index 1024 * PCI_MSIX_ENTRY_SIZE, one entry past the table.&lt;/p&gt;
&lt;p&gt;msi_insert_desc() does range check the index, but only against the MSI
domain hwsize, which matches the table only for devices on an MSI parent
domain. With a global PCI/MSI domain hwsize is MSI_XA_DOMAIN_SIZE, so
nothing bounds the request.&lt;/p&gt;
&lt;p&gt;Cap num_msix_usable with pci_msix_vec_count().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90082</guid>
    </item>
  </channel>
</rss>
