Linux
eth: bnxt: avoid deadlock when canceling IRQ affinity notifier
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= c214410c47d6ec3128143370747d9e388bab21d7, < d10e73572cda4af7487f82f58a7771f18cf61084
- >= c214410c47d6ec3128143370747d9e388bab21d7, < 8b1118fc5a5d2cdc21cc07b5106921ad4f77c544
- >= c214410c47d6ec3128143370747d9e388bab21d7, < 51e96fa31f7e7eac2cba8f854e24d36600cc040b
Fixed in d10e73572cda4af7487f82f58a7771f18cf61084, 8b1118fc5a5d2cdc21cc07b5106921ad4f77c544, 51e96fa31f7e7eac2cba8f854e24d36600cc040b
- 6.15
Fixed in 0, 6.18.57, 7.1.10, 7.2
Mitigation
Upgrade Linux to d10e73572cda4af7487f82f58a7771f18cf61084 or 8b1118fc5a5d2cdc21cc07b5106921ad4f77c544 or 51e96fa31f7e7eac2cba8f854e24d36600cc040b or later.
Upgrade Linux to 0 or 6.18.57 or 7.1.10 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.