← All Advisories
Reported from OT-Advisories.com as of

Linux Linux Kernel Vulnerability Exposed to Unauthenticated Network Attackers

Last refreshed2026-10-15

Status: UPDATED  |  Advisory ID: CVE-2026-74745

Key Details

CVECVE-2026-74745
CVSS Score / Version
7.5 (High) / CVSS v3.1
Updated2026-10-15
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS Prose
attack vector is network; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is none; integrity impact is none; availability impact is high.
Affected products
Linux Kernel
Exploitation prediction (EPSS)
0.49% probability of exploitation in the next 30 days (41% percentile) -- FIRST.org's EPSS model.

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-74745
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-74745
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.