Menu

Star on GitHub · 3.2k

CVE-2026-74389

In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Fix log flood after cmd_mbox failure hns_roce_cmd_mbox() is the command interface between driver and hardware.

Published Aug 15, 2026EPSS 0.21%

Overview

CVE-2026-74389 is a known-severity vulnerability. It was published on August 15, 2026.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

RDMA/hns: Fix log flood after cmd_mbox failure

hns_roce_cmd_mbox() is the command interface between driver and

hardware. When hardware is abnormal, the unlimited error printings

after hns_roce_cmd_mbox() failure will cause log flood and even

system crash.

Replace ibdev_err() and ibdev_warn() with their ratelimited versions

in the error handling path after hns_roce_cmd_mbox() (and its wrappers

hns_roce_create_hw_ctx/hns_roce_destroy_hw_ctx) fails.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-74389?

CVE-2026-74389 is a known-severity vulnerability. It was published on August 15, 2026.

How severe is CVE-2026-74389?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-74389?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-74389?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-74389 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.