In the Linux kernel, the following vulnerability has been resolved: NTB: epf: Avoid calling pci_irq_vector() from hardirq context ntb_epf_vec_isr()… (CVE-2026-64430)
A vulnerability in the Linux kernel's NTB epf driver involved calling pci_irq_vector() from a hardirq context, which can lead to a 'scheduling while atomic' kernel bug. This occurs because pci_irq_vector() calls msi_get_virq(), which takes a mutex and is not safe to call in atomic context. The issue has been resolved by caching the IRQ number and avoiding the problematic call in the interrupt service routine.
AI Analysis
Technical Summary
The Linux kernel NTB epf driver had a vulnerability where the interrupt service routine ntb_epf_vec_isr() called pci_irq_vector() from hardirq context. pci_irq_vector() internally calls msi_get_virq(), which acquires a mutex, causing a 'scheduling while atomic' kernel bug. This bug manifests as kernel crashes or instability due to improper locking in atomic context. The fix involves caching the Linux IRQ number during vector allocation and using this cached value in the ISR to avoid calling pci_irq_vector() in atomic context. Running the ISR in a threaded IRQ handler was considered but deemed unnecessary.
Potential Impact
This vulnerability can cause kernel crashes or instability due to improper scheduling in atomic context, potentially leading to denial of service on affected systems. There is no indication of privilege escalation or code execution impact. No known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by caching the IRQ number and avoiding unsafe calls in the interrupt context. Users should update to the Linux kernel version that includes this fix once it is released. Patch status is not explicitly confirmed in the provided data; therefore, check the official Linux kernel advisories or vendor updates for the exact fixed versions and apply them accordingly.
In the Linux kernel, the following vulnerability has been resolved: NTB: epf: Avoid calling pci_irq_vector() from hardirq context ntb_epf_vec_isr()… (CVE-2026-64430)
Description
A vulnerability in the Linux kernel's NTB epf driver involved calling pci_irq_vector() from a hardirq context, which can lead to a 'scheduling while atomic' kernel bug. This occurs because pci_irq_vector() calls msi_get_virq(), which takes a mutex and is not safe to call in atomic context. The issue has been resolved by caching the IRQ number and avoiding the problematic call in the interrupt service routine.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel NTB epf driver had a vulnerability where the interrupt service routine ntb_epf_vec_isr() called pci_irq_vector() from hardirq context. pci_irq_vector() internally calls msi_get_virq(), which acquires a mutex, causing a 'scheduling while atomic' kernel bug. This bug manifests as kernel crashes or instability due to improper locking in atomic context. The fix involves caching the Linux IRQ number during vector allocation and using this cached value in the ISR to avoid calling pci_irq_vector() in atomic context. Running the ISR in a threaded IRQ handler was considered but deemed unnecessary.
Potential Impact
This vulnerability can cause kernel crashes or instability due to improper scheduling in atomic context, potentially leading to denial of service on affected systems. There is no indication of privilege escalation or code execution impact. No known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by caching the IRQ number and avoiding unsafe calls in the interrupt context. Users should update to the Linux kernel version that includes this fix once it is released. Patch status is not explicitly confirmed in the provided data; therefore, check the official Linux kernel advisories or vendor updates for the exact fixed versions and apply them accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-wwc2-fvch-vwhh
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64430"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a6542099c2644c7f80832d1
Added to database: 07/25/2026, 23:08:57 UTC
Last enriched: 07/25/2026, 23:22:14 UTC
Last updated: 07/26/2026, 04:11:57 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.