In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix NULL pointer dereference PCIe errors detected by a Root Port or… (CVE-2026-53177)
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.
AI Analysis
Technical Summary
The Linux kernel bnxt_en driver had a vulnerability where PCIe error recovery routines could dereference a NULL pointer. Specifically, the .error_detected() callback bnxt_io_error_detected() disables and synchronizes IRQs by mapping completion rings to IRQs using bp->bnapi. Since bp->bnapi is allocated on NIC open and freed on NIC close, error recovery on a closed NIC could cause a NULL pointer dereference. The patch adds a check to ensure bp->bnapi is not NULL before disabling and synchronizing IRQs.
Potential Impact
This vulnerability could cause a kernel NULL pointer dereference, leading to a denial of service (system crash or kernel panic) when PCIe errors occur on a closed NIC. There is no indication of privilege escalation or code execution impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a patch is available, avoid triggering PCIe error recovery on closed NICs if possible.
In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix NULL pointer dereference PCIe errors detected by a Root Port or… (CVE-2026-53177)
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.
CVSS v3.1
Score 5.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel bnxt_en driver had a vulnerability where PCIe error recovery routines could dereference a NULL pointer. Specifically, the .error_detected() callback bnxt_io_error_detected() disables and synchronizes IRQs by mapping completion rings to IRQs using bp->bnapi. Since bp->bnapi is allocated on NIC open and freed on NIC close, error recovery on a closed NIC could cause a NULL pointer dereference. The patch adds a check to ensure bp->bnapi is not NULL before disabling and synchronizing IRQs.
Potential Impact
This vulnerability could cause a kernel NULL pointer dereference, leading to a denial of service (system crash or kernel panic) when PCIe errors occur on a closed NIC. There is no indication of privilege escalation or code execution impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a patch is available, avoid triggering PCIe error recovery on closed NICs if possible.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-fgqh-527q-6hx4
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53177"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- 3.1
Threat ID: 6a498a7727e9c7971936eec9
Added to database: 07/04/2026, 22:34:31 UTC
Last enriched: 07/04/2026, 22:38:12 UTC
Last updated: 07/31/2026, 19:24:47 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.