bnxt_en: Fix NULL pointer dereference
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e5811b8c09df9bc80eabc95339fceded23f16289 · < 3884976f87448e269908ae61bd5d62d54ce9c0c7| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s bnxt_en driver can dereference a NULL pointer during PCIe error recovery if the NIC is closed. This can disrupt kernel operation; the input does not establish how an attacker could trigger the PCIe error or whether authentication or user interaction is required.
Engineers running Linux systems with the bnxt_en driver should check their kernel versions; affected versions were not provided.