CVE-2026-72496
Linux kernel vulnerability
- Published15 Aug 2026
Description
In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Proper rollback if the ioremap fails bnxt_qplib_alloc_dpi returns success even if ioremap fails. Add the proper rollback when the ioremap fails and return -ENOMEM status.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/00444baa8f74d220764ee5903f60759c120cabd5
- https://git.kernel.org/stable/c/303f6fef95df5e5316970746d861cf6daeeca77f
- https://git.kernel.org/stable/c/3c69ff7f4a761e18ce8abfa0c98e12097b39adaa
- https://git.kernel.org/stable/c/87267803a8c824616eb147c5dad7030a5db6f878
- https://git.kernel.org/stable/c/f956477c343aa73e9d9c8d6ebf32efac7cd4f4e2
Frequently asked
Is CVE-2026-72496 being actively exploited?
CVE-2026-72496 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.14%.
How severe is CVE-2026-72496?
CVE-2026-72496 has a CVSS 3.1 base score of 9.2, rated critical. EPSS estimates a 0.14% probability of exploitation.
How do I fix CVE-2026-72496?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-72496 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.