CVE-2026-74389: RDMA/hns: Fix log flood after cmd_mbox failure
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 66f44ec974ab372e4e1ee9eac4245237c94e8f68, 7d9fbee252f84de3e6947a40eec01481c9d8afbb, a194e535019e0b32831f16b0eafd83c54d57ccbb.
Low priority for now. Upgrade to Linux Linux 66f44ec974ab372e4e1ee9eac4245237c94e8f68, 7d9fbee252f84de3e6947a40eec01481c9d8afbb, a194e535019e0b32831f16b0eafd83c54d57ccbb or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.9affected
- 9a4435375cd151e07c0c38fa601b00115986091b and later · before a194e535019e0b32831f16b0eafd83c54d57ccbbaffected · git
- 9a4435375cd151e07c0c38fa601b00115986091b and later · before a6c5f5d98719e69228512390d5db3bf4b6468064affected · git
- 9a4435375cd151e07c0c38fa601b00115986091b and later · before 7d9fbee252f84de3e6947a40eec01481c9d8afbbaffected · git
- 9a4435375cd151e07c0c38fa601b00115986091b and later · before 66f44ec974ab372e4e1ee9eac4245237c94e8f68affected · git
- 9a4435375cd151e07c0c38fa601b00115986091b and later · before f3c9e84268e9fa613d40d6c138fb6969c35879b5affected · git
- 9a4435375cd151e07c0c38fa601b00115986091b and later · before bbd97d71e53e551890e4115ad9de46b5f2ac0858affected · git
- before 4.9not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74387Aug 15, 2026 · ALSA: seq: midi: Serialize output teardown with event_input31Monitor
- ← EarlierCVE-2026-74388Aug 15, 2026 · ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data31Monitor
- Later →CVE-2026-74390Aug 15, 2026 · RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 66f44ec974ab372e4e1ee9eac4245237c94e8f68 | Vendor (CNA) |
| Linux Linux | 7d9fbee252f84de3e6947a40eec01481c9d8afbb | Vendor (CNA) |
| Linux Linux | a194e535019e0b32831f16b0eafd83c54d57ccbb | Vendor (CNA) |
| Linux Linux | a6c5f5d98719e69228512390d5db3bf4b6468064 | Vendor (CNA) |
| Linux Linux | bbd97d71e53e551890e4115ad9de46b5f2ac0858 | Vendor (CNA) |
| Linux Linux | f3c9e84268e9fa613d40d6c138fb6969c35879b5 | Vendor (CNA) |
| debian:linux | 6.12.100-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/7d9fbee252f84de3e6947a40eec01481c9d8afbb
- git.kernel.org/stable/c/a194e535019e0b32831f16b0eafd83c54d57ccbb
- git.kernel.org/stable/c/a6c5f5d98719e69228512390d5db3bf4b6468064
- git.kernel.org/stable/c/bbd97d71e53e551890e4115ad9de46b5f2ac0858
- git.kernel.org/stable/c/f3c9e84268e9fa613d40d6c138fb6969c35879b5
Vendor advisories and official records. Exploit/PoC links are deliberately left out.