CVE-2026-74745

eth: bnxt: avoid deadlock when canceling IRQ affinity notifier

Published Aug 26, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The bnxt network driver in the Linux kernel contains a deadlock issue that occurs when an IRQ affinity notifier is unregistered. The callback executed during unregistration holds the netdev instance lock and then attempts to cancel work under the same lock. Because the work cancellation and queue restart happen while the lock is still held, the system can enter a deadlock, halting network packet processing and potentially causing the driver to become unresponsive.

Affected Systems

Any Linux kernel build that includes the pre‑patch version of the bnxt driver is vulnerable. Systems using older kernel releases that have not yet incorporated the commit that reverses the notifier registration order and moves the queue restart to a separate service task are at risk.

Risk and Exploitability

The vulnerability has a CVSS score of 7.5 and an EPSS score of < 1%, indicating a very low probability of exploitation. It is not listed in the CISA KEV catalog, indicating no known public exploitation. Exploitation would likely require an attacker to trigger a driver unload or reload with privileged kernel access, making remote unauthenticated attacks infeasible. Nevertheless, an accidental deadlock can interrupt critical network operations, leading to service outage and impacting availability. Prompt remediation is recommended to prevent potential downtime.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Linux kernel update that incorporates the bnxt driver patch addressing the race condition and deadlock weaknesses.
  • Reload the bnxt network driver or reboot the system to clear any lingering locks and ensure the updated code is active.
  • Monitor system and network logs for signs of lock contention or driver restarts that may indicate a remaining deadlock.

Generated by OpenCVE AI on August 28, 2026 at 16:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-668
Type Values Removed Values Added
Weaknesses CWE-668
Type Values Removed Values Added
Weaknesses CWE-776
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
Weaknesses CWE-776
Type Values Removed Values Added
Description 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.
Title eth: bnxt: avoid deadlock when canceling IRQ affinity notifier
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 16, 2026, 7:26 PM
Reserved
Aug 15, 2026, 5:44 AM
Status
Received
Published
Aug 26, 2026, 3:16 PM
Modified
Oct 16, 2026, 8:17 PM
Severity
Low
Public date
Aug 26, 2026, 12:00 AM