CVE-2026-74745

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

August 26, 2026

Last Modified

August 27, 2026

Advisory Details (2)

Auto-updated Aug 27, 2026
No patch confirmed yet.
generic

eth: bnxt: avoid deadlock when canceling IRQ affinity notifier - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b1118fc5a5d2cdc21cc07b5106921ad4f77c544
generic

eth: bnxt: avoid deadlock when canceling IRQ affinity notifier - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51e96fa31f7e7eac2cba8f854e24d36600cc040b

Vendor Advisories for CVE-2026-74745(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 15× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 19:15 UTCGHSA enrichment
  3. 2026-08-29 07:06 UTCEG score recompute
  4. 2026-08-29 07:05 UTCGHSA enrichment
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-28 18:54 UTCGHSA enrichment
  7. 2026-08-28 06:44 UTCGHSA enrichment
  8. 2026-08-27 18:31 UTCEG score recompute
  9. 2026-08-27 18:31 UTCGHSA enrichment
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-27 06:22 UTCEG score recompute▲ 7.50
  12. 2026-08-27 06:11 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  13. 2026-08-26 15:43 UTCNVD update
  14. 2026-08-26 14:44 UTCEG score recompute
  15. 2026-08-26 14:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74745?
CVE-2026-74745 is a high vulnerability published on August 26, 2026. 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…
When was CVE-2026-74745 disclosed?
CVE-2026-74745 was first published in the National Vulnerability Database on August 26, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74745 actively exploited?
CVE-2026-74745 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.3% of all scored CVEs.
What is the CVSS score of CVE-2026-74745?
CVE-2026-74745 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-74745?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74745, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-74745

Explore →

Is Your Infrastructure Affected by CVE-2026-74745?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs