# CVE-2026-74745: linux: In the Linux kernel, the following vulnerability has been resolved: eth: bnxt: avoid deadlock when canceling IRQ aff... CVE-2026-74745 is fixed in 14 products on 1 platform, first by DEBIAN-CVE-2026-74745, released September 4, 2026. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2026-74745 - Priority: High - CVSS: 7.5 (high) - EPSS: 0.0045 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Aug 26, 2026 ## 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. ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | dtb-aarch64 opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-64kb opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-64kb sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-azure opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-azure sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-default opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-default sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24197-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24197-1.md) | Nov 7, 2026 | | Linux | kernel-default-base opensuse-leap 16.0 | 6.12.0-160000.39.1.160000.2.25 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-default-base sles 16.0 | 6.12.0-160000.39.1.160000.2.26 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-docs opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-docs sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-kvmsmall opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-kvmsmall sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-obs-build opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-obs-qa opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-obs-qa sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-rt opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-source opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-source sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-syms opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-syms sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | kernel-zfcpdump opensuse-leap 16.0 | 6.12.0-160000.39.1 | [OPENSUSE-SU-2026:22091-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22091-1.md) | Nov 7, 2026 | | Linux | kernel-zfcpdump sles 16.0 | 6.12.0-160000.39.1 | [SUSE-SU-2026:24235-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24235-1.md) | Nov 7, 2026 | | Linux | linux Debian 14 | 7.1.10-1 | [DEBIAN-CVE-2026-74745](https://patchblox.com/security/data/fix/linux/debian-cve-2026-74745.md) | Sep 4, 2026 | --- Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.