What is CVE-2026-74745?

CVE-2026-74745 is a High severity Linux kernel vulnerability with a CVSS score of 7.5 out of 10, affecting Linux kernel versions from 6.15 onward and patched in 7.1.10 and 7.2. CVE-2026-74745 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-74745?

CVE-2026-74745 has a CVSS score of 7.5 out of 10, rated High severity. The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2026-74745?

Yes, CVE-2026-74745 has been patched. Fixed versions include 7.1.10 and 7.2. If you are running Linux kernel 6.15 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-74745 actively exploited?

CVE-2026-74745 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-74745

High

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.

Package Linux Kernel

Published 2026-08-26

Last modified 2026-08-27

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.5

out of 10

High

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected versions

Linux kernel versions 6.15 and later are affected. Fixed in 7.1.10, 7.2 and their respective stable series.

Affected from

≥ 6.15

Fixed in

✓ 7.1.10 7.1.x ✓ 7.2

References

2 total

Details

CVE ID CVE-2026-74745

Severity High

CVSS score 7.5 / 10

CVSS version 3.1

Published 2026-08-26

Modified 2026-08-27

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-74745?

CVE-2026-74745 is a High severity Linux kernel vulnerability with a CVSS score of 7.5 out of 10 . It affects Linux kernel versions from 6.15 onward and has been patched in 7.1.10 and 7.2. CVE-2026-74745 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-74745?

CVE-2026-74745 has a CVSS score of 7.5 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2026-74745?

Yes. CVE-2026-74745 has been patched. Fixed versions include 7.1.10 and 7.2. If you are running Linux kernel 6.15 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-74745 actively exploited?

No. CVE-2026-74745 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.