CVE-2026-74745

CVE-2026-74745 · eth: bnxt: avoid deadlock when canceling IRQ affinity notifier

CVSS 7.5 · Высокий · EPSS 0,5% · Есть исправление

dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="linux"'

dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="linux-hwe-edge"'

dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="linux-aws-5.0"'

curl -fsSL https://ru.patchfirst.dev/check.sh | sh

Здесь приведены факты из открытых источников об уязвимостях. Перед обновлением ознакомьтесь с исходным сообщением.

На странице показана часть фактов из источников. Полное описание и список затронутых версий приведены в связанных бюллетенях.

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.

Опубликовано

2026-08-26T14:36:55.372Z

Обновлено

2026-10-16T19:26:23.647Z

Стек: system

Проверьте свой сервер →