eth: bnxt: avoid deadlock when canceling IRQ affinity notifier

Summary

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.

Timeline

1. Aug 26, 2026, 2:36 PM UTCCVE published
2. Oct 16, 2026, 7:16 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. Oct 16, 2026, 7:26 PM UTCRecord last updated

Affected versions

• Linux Linux

  From c214410c47d6ec3128143370747d9e388bab21d7 · fixed in d10e73572cda4af7487f82f58a7771f18cf61084; From c214410c47d6ec3128143370747d9e388bab21d7 · fixed in 8b1118fc5a5d2cdc21cc07b5106921ad4f77c544; From c214410c47d6ec3128143370747d9e388bab21d7 · fixed in 51e96fa31f7e7eac2cba8f854e24d36600cc040b

• Linux Linux

  6.15

• KernelLinux

  From 6.15.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.1.10

References 3