Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64430: NTB: epf: Avoid calling pci_irq_vector() from hardirq context

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.49% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 174a97f21bf9c54fa37ec0f321692e862ea130a3, 1dba8444ac0100133d72374634f6d7451fff1ccc, 33bba331a4a5fee8b6026fe72eca13cceeec1b7b.

Low priority for now. Upgrade to Linux Linux 174a97f21bf9c54fa37ec0f321692e862ea130a3, 1dba8444ac0100133d72374634f6d7451fff1ccc, 33bba331a4a5fee8b6026fe72eca13cceeec1b7b or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Jul 25, 2026
Updated
Sep 3, 2026
EPSS
0.4% · 41th percentile
CWE
—

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CNA vs NVD score

NVD
—
CNA · Linux
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-64430

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.12 and later · before 5.15.212
  • linux linux kernel5.16 and later · before 6.1.178
  • linux linux kernel6.2 and later · before 6.6.145
  • linux linux kernel6.7 and later · before 6.12.96
  • linux linux kernel6.13 and later · before 6.18.39
  • linux linux kernel6.19 and later · before 7.1.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.12affected
    • 812ce2f8d14ea791edd88c36ebcc9017bf4c88cb and later · before 33bba331a4a5fee8b6026fe72eca13cceeec1b7baffected · git
    • 812ce2f8d14ea791edd88c36ebcc9017bf4c88cb and later · before aff271b12a1eb8c8b3da19223ae1a6abe1e8168baffected · git
    • 812ce2f8d14ea791edd88c36ebcc9017bf4c88cb and later · before 1dba8444ac0100133d72374634f6d7451fff1cccaffected · git
    • 812ce2f8d14ea791edd88c36ebcc9017bf4c88cb and later · before 174a97f21bf9c54fa37ec0f321692e862ea130a3affected · git
    • 812ce2f8d14ea791edd88c36ebcc9017bf4c88cb and later · before f71e8d9875069fa73e335f63f02ec6e52e3aaa51affected · git
    • 812ce2f8d14ea791edd88c36ebcc9017bf4c88cb and later · before 6350df503897d57c5634f71b0767d48c3b837583affected · git
    • 812ce2f8d14ea791edd88c36ebcc9017bf4c88cb and later · before 4dcddc1c794d1c65eda68f1f8dd04a0fecc0870faffected · git
    • before 5.12not affected · semver
    • 5.15.212 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:12linux-6.12before 6.12.100-1~deb12u16.12.100-1~deb12u1
Debian:13linuxbefore 6.12.96-16.12.96-1
Debian:14linuxbefore 7.1.4-17.1.4-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-64428Jul 25, 2026 · gpio: sch: use raw_spinlock_t in the irq startup path
    22Monitor
  • ← EarlierCVE-2026-64429Jul 25, 2026 · gpio: eic-sprd: use raw_spinlock_t in the irq startup path
    22Monitor
  • Later →CVE-2026-64431Jul 25, 2026 · ntfs: avoid calling post_write_mst_fixup() for invalid index_block
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux174a97f21bf9c54fa37ec0f321692e862ea130a3Vendor (CNA)
Linux Linux1dba8444ac0100133d72374634f6d7451fff1cccVendor (CNA)
Linux Linux33bba331a4a5fee8b6026fe72eca13cceeec1b7bVendor (CNA)
Linux Linux4dcddc1c794d1c65eda68f1f8dd04a0fecc0870fVendor (CNA)
Linux Linux6350df503897d57c5634f71b0767d48c3b837583Vendor (CNA)
Linux Linuxaff271b12a1eb8c8b3da19223ae1a6abe1e8168bVendor (CNA)
Linux Linuxf71e8d9875069fa73e335f63f02ec6e52e3aaa51Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records