CVE-2026-64430NTB: epf: Avoid calling pci_irq_vector() from hardirq context
- 7.5HighCVSS base score
- 0.49%Exploitation in 30 daysEPSS · top 57% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 23 days later
· 23 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Analyzed | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.49% · top 57% of all CVEs (13 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.
Affected products
- affected 812ce2f8d14ea791edd88c36ebcc9017bf4c88cb – < 33bba331a4a5fee8b6026fe72eca13cceeec1b7b
- affected 812ce2f8d14ea791edd88c36ebcc9017bf4c88cb – < aff271b12a1eb8c8b3da19223ae1a6abe1e8168b
- affected 812ce2f8d14ea791edd88c36ebcc9017bf4c88cb – < 1dba8444ac0100133d72374634f6d7451fff1ccc
- affected 812ce2f8d14ea791edd88c36ebcc9017bf4c88cb – < 174a97f21bf9c54fa37ec0f321692e862ea130a3
- affected 812ce2f8d14ea791edd88c36ebcc9017bf4c88cb – < f71e8d9875069fa73e335f63f02ec6e52e3aaa51
- affected 812ce2f8d14ea791edd88c36ebcc9017bf4c88cb – < 6350df503897d57c5634f71b0767d48c3b837583
- affected 812ce2f8d14ea791edd88c36ebcc9017bf4c88cb – < 4dcddc1c794d1c65eda68f1f8dd04a0fecc0870f
- affected 5.12
- unaffected < 5.12
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.96 – ≤ 6.12.*
- unaffected 6.18.39 – ≤ 6.18.*
- unaffected 7.1.4 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References7
- https://git.kernel.org/stable/c/33bba331a4a5fee8b6026fe72eca13cceeec1b7b (opens in a new tab)
- https://git.kernel.org/stable/c/aff271b12a1eb8c8b3da19223ae1a6abe1e8168b (opens in a new tab)
- https://git.kernel.org/stable/c/1dba8444ac0100133d72374634f6d7451fff1ccc (opens in a new tab)
- https://git.kernel.org/stable/c/174a97f21bf9c54fa37ec0f321692e862ea130a3 (opens in a new tab)
- https://git.kernel.org/stable/c/f71e8d9875069fa73e335f63f02ec6e52e3aaa51 (opens in a new tab)
- https://git.kernel.org/stable/c/6350df503897d57c5634f71b0767d48c3b837583 (opens in a new tab)
- https://git.kernel.org/stable/c/4dcddc1c794d1c65eda68f1f8dd04a0fecc0870f (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-48774 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64430)Record last updated .