CVE-2026-64430

NTB: epf: Avoid calling pci_irq_vector() from hardirq context

HIGH
7.5
CVSS Score
Published: July 25, 2026 at 08:51 AM UTC
Updated: September 3, 2026 at 06:44 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.5%

Description

In the Linux kernel, the following vulnerability has been resolved: NTB: epf: Avoid calling pci_irq_vector() from hardirq context ntb_epf_vec_isr() calls pci_irq_vector() in hardirq context to derive the vector number. pci_irq_vector() calls msi_get_virq() that takes a mutex and can therefore trigger "scheduling while atomic" splats: BUG: scheduling while atomic: kworker/u33:0/55/0x00010001 ... Call trace: ... schedule+0x38/0x110 schedule_preempt_disabled+0x28/0x50 __mutex_lock.constprop.0+0x848/0x908 __mutex_lock_slowpath+0x18/0x30 mutex_lock+0x4c/0x60 msi_domain_get_virq+0xe8/0x138 pci_irq_vector+0x2c/0x60 ntb_epf_vec_isr+0x28/0x120 [ntb_hw_epf] __handle_irq_event_percpu+0x70/0x3a8 handle_irq_event+0x48/0x100 handle_edge_irq+0x100/0x1c8 ... Cache the Linux IRQ number for vector 0 when vectors are allocated and use it as a base in the ISR. Running the ISR in a threaded IRQ handler would also avoid the problem, but that would be unnecessary here.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.12 ≤ v < 5.15.2125.12 ≤ v < 6.1.1785.12 ≤ v < 6.12.965.12 ≤ v < 6.18.395.12 ≤ v < 6.6.1455.12 ≤ v < 7.1.45.12 ≤ v < 7.25.16 ≤ v < 6.1.1786.13 ≤ v < 6.18.396.19 ≤ v < 7.1.46.2 ≤ v < 6.6.1456.7 ≤ v < 6.12.965.12812ce2f8d14ea791edd88c36ebcc9017bf4c88cb
Vendor states this is fixed in 174a97f21bf9c54fa37ec0f321692e862ea130a3 (fixed)
Vendor states this is fixed in 1dba8444ac0100133d72374634f6d7451fff1ccc (fixed)
Vendor states this is fixed in 33bba331a4a5fee8b6026fe72eca13cceeec1b7b (fixed)
Vendor states this is fixed in 4dcddc1c794d1c65eda68f1f8dd04a0fecc0870f (fixed)
Vendor states this is fixed in 6350df503897d57c5634f71b0767d48c3b837583 (fixed)
Vendor states this is fixed in aff271b12a1eb8c8b3da19223ae1a6abe1e8168b (fixed)
Vendor states this is fixed in f71e8d9875069fa73e335f63f02ec6e52e3aaa51 (fixed)
Vendor states this is fixed in 5.12 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

CVSS

7.5HIGHLinux
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card