CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HHigh (7.5) in linux linux. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExplain CVE-2026-74745 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-74745?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-74745?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-74745 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 6.15 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.18 | 6.18.57 |
| Linux | 7.1 | 7.1.10 |
| Linux | later releases | 7.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | 7.1.10-1 | DEBIAN-CVE-2026-74745 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-74745 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-74745 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-74745 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2026-74745 |
| Ubuntu | 24.04:LTS | linux-aws-7.0 | 7.0.0-1017.18~24.04.1 | UBUNTU-CVE-2026-74745 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1019.19~24.04.1 | UBUNTU-CVE-2026-74745 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-gcp-7.0 | 7.0.0-1017.19~24.04.1 | UBUNTU-CVE-2026-74745 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-hwe-7.0 | 7.0.0-42.42~24.04.1 | UBUNTU-CVE-2026-74745 USN-8959-1 |
| Ubuntu | 24.04:LTS | linux-oracle-7.0 | 7.0.0-1016.18~24.04.1 | UBUNTU-CVE-2026-74745 USN-9020-1 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-oem-6.8, linux-aws-6.14 and 27 more | no fix listed | UBUNTU-CVE-2026-74745 |
| Ubuntu | 24.04:LTS | linux-riscv-7.0 | 7.0.0-42.42.1~24.04.1 | UBUNTU-CVE-2026-74745 |
| Ubuntu | 26.04:LTS | linux | 7.0.0-42.42 | UBUNTU-CVE-2026-74745 USN-8959-1 |
| 12 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| SUSE | Linux Enterprise High Availability Extension 16.0 | kernel-default | 6.12.0-160000.39.1 | SUSE-SU-2026:24197-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | kernel-64kb, kernel-docs, kernel-syms and 6 more | 6.12.0-160000.39.1 | SUSE-SU-2026:24235-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | kernel-default-base | 6.12.0-160000.39.1.160000.2.26 | SUSE-SU-2026:24235-1 |
| SUSE | Linux Enterprise Server for NVIDIA 16.1 | kernel-nvidia64kb, kernel-source-nvidia | 6.12.0-160100.6.1 | SUSE-SU-2026:24691-1 |
| SUSE | Linux Micro 6.2 | kernel-default-base | 6.12.0-160000.39.1.160000.2.26 | SUSE-SU-2026:24184-1 |
| SUSE | Linux Micro 6.2 | kernel-rt, kernel-64kb, kernel-source and 1 more | 6.12.0-160000.39.1 | SUSE-SU-2026:24184-1 |
| SUSE | Linux Micro Extras 6.2 | kernel-syms, kernel-obs-build | 6.12.0-160000.39.1 | SUSE-SU-2026:24179-1 |
| openSUSE | Leap 16.0 | kernel-default-base | 6.12.0-160000.39.1.160000.2.25 | openSUSE-SU-2026:22091-1 |
| openSUSE | Leap 16.0 | kernel-rt, dtb-aarch64, kernel-64kb and 9 more | 6.12.0-160000.39.1 | openSUSE-SU-2026:22091-1 |
| openSUSE | Leap 16.1 | kernel-default-base | 6.12.0-160100.9.1.160100.3.14 | openSUSE-SU-2026:22309-1 |
| openSUSE | Leap 16.1 | kernel-nvidia64kb, kernel-syms-nvidia, kernel-source-nvidia | 6.12.0-160100.6.1 | openSUSE-SU-2026:22313-1 |
| openSUSE | Leap 16.1 | kernel-rt, dtb-aarch64, kernel-64kb and 9 more | 6.12.0-160100.9.1 | openSUSE-SU-2026:22309-1 |
| Alpaquita | stream | linux-lts | 6.18.58-r0 | BELL-CVE-2026-74745 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.
Red Hat rates this Low.
A flaw of low impact was found in the Linux kernel's Broadcom bnxt Ethernet driver. Unregistering an IRQ affinity notifier waits for the notifier callback synchronously, and the bnxt driver takes the netdev instance lock in that callback while also canceling the queued restart work under the same lock. This lock ordering can deadlock. A local attacker with the ability to trigger IRQ affinity changes on a system using affected bnxt hardware with TPH (Target Prefetch Hints) support could exploit this to cause a kernel deadlock that leaves the system unresponsive, resulting in denial of service. Confidentiality and integrity are not affected.
The vulnerable code was introduced together with TPH support in the bnxt driver and is present in Red Hat Enterprise Linux 9 and Red Hat Enterprise Linux 10 as well as in Red Hat In-Vehicle OS, which are therefore affected. Red Hat Enterprise Linux 6, 7, and 8, and the initial Red Hat Enterprise Linux 10.0 release, do not contain the vulnerable code and are not affected. Fixes for the affected streams are currently deferred to a future update. The residual risk of this deferral is limited: the flaw is not remotely triggerable and is not caused by normal network traffic, so exploitation requires local access with the ability to change IRQ affinity on the affected device.
Red Hat rates this flaw as Low impact, with a Red Hat CVSS 3.1 score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). This differs from the upstream CVE record severity of Important (CVSS 7.5, AV:N), which assumes network reachability; the deadlock is in fact only triggerable locally through IRQ affinity notifier operations on affected bnxt hardware.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel-rt | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-74745.