CVE-2026-74745High· 7.5▾ Twilight

In the Linux kernel, the following vulnerability has been resolved: eth: bnxt: avoid deadlock when canceling IRQ affinity notifier Unregistering IRQ affinity notifiers waits for the callback synchronously. bnxt takes the netdev instanc…

▾ Twilight zone — High severity, or a signal on a lesser flaw

Depth score41/ 100 · Moderate

impact 41.3 · likelihood 0.1 · exploitation 0

⚡ Agent-ready:Raw markdown ↗JSON ↗

Proof of concept

Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.

…

Published

Aug 26, 2026

Updated

Oct 16, 2026

CVSS

7.5

Vendor

Linux

Product

Linux

CWE

—

Depth score

41 · Moderate

EPSS

0.45% · p39

Platforms

—

Source

NVD

Vector

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

CISA SSVC

decided 2026-10-16

Exploitation: none
Automatable: yes
Technical impact: partial

Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.

EPSS history

Exploit-prediction probability, daily snapshots since Oct 15.

0.5% → 0.5%

Timeline

Disclosure to exploitation, from the record and what we observed since indexing it.

4 events · 52 days

Aug 26, 2026Published
Disclosed via NVD
Oct 15, 2026EPSS first tracked
0.5%
Oct 16, 2026Record revised
Last analysed / modified upstream
Oct 17, 2026EPSS peak
0.5% → 0.6%

Linux #nvd #cve.org

Affected

Linux >= c214410c47d6ec3128143370747d9e388bab21d7 < d10e73572cda4af7487f82f58a7771f18cf61084
Linux >= c214410c47d6ec3128143370747d9e388bab21d7 < 8b1118fc5a5d2cdc21cc07b5106921ad4f77c544
Linux >= c214410c47d6ec3128143370747d9e388bab21d7 < 51e96fa31f7e7eac2cba8f854e24d36600cc040b
Linux 6.15

Full technical detail▾

Overview

In the Linux kernel, the following vulnerability has been resolved:

eth: bnxt: avoid deadlock when canceling IRQ affinity notifier

Unregistering IRQ affinity notifiers waits for the callback synchronously. bnxt takes the netdev instance lock in the notifier (to restart the queue) and cancels the work under the same lock. This may obviously deadlock.

Move the restart to the async service task. The queue restart isn't super time sensitive. Store the new TPH tag, schedule the task. Safely canceling the service task is already ironed out.

In bnxt_request_irq() the order of registering notifier, affinity and initial TPH programming has to be inverted. I think it was racy previously since user may trigger an update as soon as notifier is installed.

There's a small known gap - if pcie_tph_get_cpu_st() fails at init and the target tag is 0 we may miss programming the entry. This does not seem worth fixing, the code has skip-on-failure all over the place, anyway.

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

References

Related vulnerabilities

Connected by shared product, vendor, weakness, or advisory.

#nvd#cve.org