Skip to content
Systems

CVE-2026-72497

8.8
High
EPSS 0.12%Patch availableAug 17, 2026

bnxt_re RDMA driver WQE slot validation flaw allows kernel memory corruption.

common questions

Is CVE-2026-72497 being exploited?

Not confirmed. CVE-2026-72497 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.12% probability of exploitation in the next 30 days.

How severe is CVE-2026-72497?

CVE-2026-72497 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-72497?

Yes. A fix has been recorded for CVE-2026-72497. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-72497 affect?

CVE-2026-72497 affects Linux kernel (bnxt_re RDMA driver), Servers with Broadcom bnxt/bnxt_re NICs, Distributions shipping affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72497?

Install vendor/distro kernel or bnxt_re driver updates immediately.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (bnxt_re RDMA driver)Servers with Broadcom bnxt/bnxt_re NICsDistributions shipping affected kernels
impact

Malformed WQE slot values can trigger kernel memory corruption in bnxt_re, enabling local privilege escalation or causing system crash (DoS).

action required

Patch when possible

affected versions
Linux Linux
  • affected>= d8ea645d6984c84a87032063a0941f15a323831f and < a59d815cbe667929b693b5fa6716a074e6a31c5b
  • affected>= d8ea645d6984c84a87032063a0941f15a323831f and < dc95931b7e1326dacae547874bf38c092e5960d8
  • affected6.12
vendor says fixed in< 6.12, >= 7.1.5 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free