CVE-2026-64430
NTB: epf: Avoid calling pci_irq_vector() from hardirq context
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.
INFO
Published Date :
July 25, 2026, 10:17 a.m.
Last Modified :
July 25, 2026, 10:17 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64430
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update the Linux kernel.
- Apply the patch for "NTB: epf: Avoid calling pci_irq_vector() from hardirq context".
- Use cached IRQ numbers in ISR.
- Avoid scheduling while atomic in interrupt context.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-64430.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-64430 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-64430
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-64430 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64430 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 25, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '812ce2f8d14ea791edd88c36ebcc9017bf4c88cb', 'lessThan': '33bba331a4a5fee8b6026fe72eca13cceeec1b7b', 'versionType': 'git'}, {'status': 'affected', 'version': '812ce2f8d14ea791edd88c36ebcc9017bf4c88cb', 'lessThan': 'aff271b12a1eb8c8b3da19223ae1a6abe1e8168b', 'versionType': 'git'}, {'status': 'affected', 'version': '812ce2f8d14ea791edd88c36ebcc9017bf4c88cb', 'lessThan': '1dba8444ac0100133d72374634f6d7451fff1ccc', 'versionType': 'git'}, {'status': 'affected', 'version': '812ce2f8d14ea791edd88c36ebcc9017bf4c88cb', 'lessThan': '174a97f21bf9c54fa37ec0f321692e862ea130a3', 'versionType': 'git'}, {'status': 'affected', 'version': '812ce2f8d14ea791edd88c36ebcc9017bf4c88cb', 'lessThan': 'f71e8d9875069fa73e335f63f02ec6e52e3aaa51', 'versionType': 'git'}, {'status': 'affected', 'version': '812ce2f8d14ea791edd88c36ebcc9017bf4c88cb', 'lessThan': '6350df503897d57c5634f71b0767d48c3b837583', 'versionType': 'git'}, {'status': 'affected', 'version': '812ce2f8d14ea791edd88c36ebcc9017bf4c88cb', 'lessThan': '4dcddc1c794d1c65eda68f1f8dd04a0fecc0870f', 'versionType': 'git'}], 'programFiles': ['drivers/ntb/hw/epf/ntb_hw_epf.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.12'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.12', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.15.212', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.178', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.145', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.96', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.39', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.4', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/ntb/hw/epf/ntb_hw_epf.c'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/174a97f21bf9c54fa37ec0f321692e862ea130a3 Added Reference https://git.kernel.org/stable/c/1dba8444ac0100133d72374634f6d7451fff1ccc Added Reference https://git.kernel.org/stable/c/33bba331a4a5fee8b6026fe72eca13cceeec1b7b Added Reference https://git.kernel.org/stable/c/4dcddc1c794d1c65eda68f1f8dd04a0fecc0870f Added Reference https://git.kernel.org/stable/c/6350df503897d57c5634f71b0767d48c3b837583 Added Reference https://git.kernel.org/stable/c/aff271b12a1eb8c8b3da19223ae1a6abe1e8168b Added Reference https://git.kernel.org/stable/c/f71e8d9875069fa73e335f63f02ec6e52e3aaa51