CVE-2026-53177
Last modified
CVE-2026-53177 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix NULL pointer dereference PCIe errors detected by a Root Port or Downstream Port cause error recovery services to run on all subordinate devices regardless of administrative state. The .error_detected() callback, bnxt_io_error_detected(), disables and synchronizes IRQs via bnxt_disable_int_sync(), which calls bnxt_cp_num_to_irq_num() to map completion rings to IRQs using bp->bnapi. Since bp->bnapi is allocated on NIC open and freed on NIC close, PCIe error recovery on a closed NIC can dereference a NULL pointer. Check if bp->bnapi is NULL before disabling and synchronizing IRQs.. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix NULL pointer dereference PCIe errors detected by a Root Port or Downstream Port cause error recovery services to run on all subordinate devices regardless of administrative state. The .error_detected() callback, bnxt_io_error_detected(), disables and synchronizes IRQs via bnxt_disable_int_sync(), which calls bnxt_cp_num_to_irq_num() to map completion rings to IRQs using bp->bnapi. Since bp->bnapi is allocated on NIC open and freed on NIC close, PCIe error recovery on a closed NIC can dereference a NULL pointer. Check if bp->bnapi is NULL before disabling and synchronizing IRQs.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.17, < 5.15.210 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.176 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.143 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.94 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.36 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53177?
How severe is CVE-2026-53177?
How do I fix CVE-2026-53177?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53171In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53172In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53173In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53174In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53175In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53176In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53178In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-53179In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-5318A weakness has been identified in LibRaw up to 0.22.0. This …4.3
- CVE-2026-53180In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53181In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53182In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-53177?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
