<?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 21:35:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43448 — nvme-pci: Fix race bug in nvme_poll_irqdisable()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43448</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;nvme-pci: Fix race bug in nvme_poll_irqdisable()&lt;/p&gt;
&lt;p&gt;In the following scenario, pdev can be disabled between (1) and (3) by
(2). This sets pdev-&amp;gt;msix_enabled = 0. Then, pci_irq_vector() will
return MSI-X IRQ(&amp;gt;15) for (1) whereas return INTx IRQ(&amp;lt;=15) for (2).
This causes IRQ warning because it tries to enable INTx IRQ that has
never been disabled before.&lt;/p&gt;
&lt;p&gt;To fix this, save IRQ number into a local variable and ensure
disable_irq() and enable_irq() operate on the same IRQ number.  Even if
pci_free_irq_vectors() frees the IRQ concurrently, disable_irq() and
enable_irq() on a stale IRQ number is still valid and safe, and the
depth accounting reamins balanced.&lt;/p&gt;
&lt;p&gt;task 1:
nvme_poll_irqdisable()
  disable_irq(pci_irq_vector(pdev, nvmeq-&amp;gt;cq_vector)) ...(1)
  enable_irq(pci_irq_vector(pdev, nvmeq-&amp;gt;cq_vector))  ...(3)&lt;/p&gt;
&lt;p&gt;task 2:
nvme_reset_work()
  nvme_dev_disable()
    pdev-&amp;gt;msix_enable = 0;  ...(2)&lt;/p&gt;
&lt;p&gt;crash log:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
Unbalanced enable for IRQ 10
WARNING: kernel/irq/manage.c:753 at __enable_irq+0x102/0x190 kernel/irq/manage.c:753, CPU#1: kworker/1:0H/26
Modules linked in:
CPU: 1 UID: 0 PID: 26 Comm: kworker/1:0H Not tainted 6.19.0-dirty #9 PREEMPT(voluntary)
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014
Workqueue: kblockd blk_mq_timeout_work
RIP: 0010:__enable_irq+0x107/0x190 kernel/irq/manage.c:753
Code: ff df 48 89 fa 48…&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;nvme-pci: Fix race bug in nvme_poll_irqdisable()&lt;/p&gt;
&lt;p&gt;In the following scenario, pdev can be disabled between (1) and (3) by
(2). This sets pdev-&amp;gt;msix_enabled = 0. Then, pci_irq_vector() will
return MSI-X IRQ(&amp;gt;15) for (1) whereas return INTx IRQ(&amp;lt;=15) for (2).
This causes IRQ warning because it tries to enable INTx IRQ that has
never been disabled before.&lt;/p&gt;
&lt;p&gt;To fix this, save IRQ number into a local variable and ensure
disable_irq() and enable_irq() operate on the same IRQ number.  Even if
pci_free_irq_vectors() frees the IRQ concurrently, disable_irq() and
enable_irq() on a stale IRQ number is still valid and safe, and the
depth accounting reamins balanced.&lt;/p&gt;
&lt;p&gt;task 1:
nvme_poll_irqdisable()
  disable_irq(pci_irq_vector(pdev, nvmeq-&amp;gt;cq_vector)) ...(1)
  enable_irq(pci_irq_vector(pdev, nvmeq-&amp;gt;cq_vector))  ...(3)&lt;/p&gt;
&lt;p&gt;task 2:
nvme_reset_work()
  nvme_dev_disable()
    pdev-&amp;gt;msix_enable = 0;  ...(2)&lt;/p&gt;
&lt;p&gt;crash log:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
Unbalanced enable for IRQ 10
WARNING: kernel/irq/manage.c:753 at __enable_irq+0x102/0x190 kernel/irq/manage.c:753, CPU#1: kworker/1:0H/26
Modules linked in:
CPU: 1 UID: 0 PID: 26 Comm: kworker/1:0H Not tainted 6.19.0-dirty #9 PREEMPT(voluntary)
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014
Workqueue: kblockd blk_mq_timeout_work
RIP: 0010:__enable_irq+0x107/0x190 kernel/irq/manage.c:753
Code: ff df 48 89 fa 48…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43448</guid>
    </item>
  </channel>
</rss>
