CVE-2026-64430 Details
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.
A vulnerability exists in the Linux kernel's handling of Non-Transparent Bridge (NTB) Endpoint Function (EPF) PCI vectors. The issue arises because the interrupt service routine (ISR) for NTB EPF vectors calls 'pci_irq_vector()' in a hard interrupt context. This can lead to 'scheduling while atomic' errors, as 'pci_irq_vector()' invokes 'msi_get_virq()', which requires a mutex. The vulnerability has been addressed by modifying the ISR to cache the IRQ number for vector 0 when vectors are allocated, and by using this cached value as a base in the ISR. The issue could also be avoided by running the ISR in a threaded IRQ handler, but this was deemed unnecessary.
The vulnerability has been fixed in the Linux kernel. Users should upgrade to the latest version of the stable Linux kernel where this issue has been addressed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/174a97f21bf9c54fa37ec0f321692e862ea130a3 | kernel.org | Patch |
| https://git.kernel.org/stable/c/1dba8444ac0100133d72374634f6d7451fff1ccc | kernel.org | Patch |
| https://git.kernel.org/stable/c/33bba331a4a5fee8b6026fe72eca13cceeec1b7b | kernel.org | Patch |
| https://git.kernel.org/stable/c/4dcddc1c794d1c65eda68f1f8dd04a0fecc0870f | kernel.org | Patch |
| https://git.kernel.org/stable/c/6350df503897d57c5634f71b0767d48c3b837583 | kernel.org | Patch |
| https://git.kernel.org/stable/c/aff271b12a1eb8c8b3da19223ae1a6abe1e8168b | kernel.org | Patch |
| https://git.kernel.org/stable/c/f71e8d9875069fa73e335f63f02ec6e52e3aaa51 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.12, < 5.15.212 >= 5.16, < 6.1.178 >= 6.2, < 6.6.145 >= 6.7, < 6.12.96 >= 6.13, < 6.18.39 >= 6.19, < 7.1.4 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 3, 2026 | Initial Analysis | [email protected] |
| Aug 17, 2026 | CVE Modified | kernel.org |
| Jul 27, 2026 | CVE Modified | kernel.org |
| Jul 25, 2026 | New CVE Received | kernel.org |