Skip to main content
VulnerabilityPublished Updated

CVE-2026-53177: Linux kernel · bnxt_en: Fix NULL pointer dereference

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d930276f2cddd0b7294cac7a8fe7b877f6d9e08d : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:49 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in d930276f2cddd0b7294cac7a8fe7b877f6d9e08d, 3884976f87448e269908ae61bd5d62d54ce9c0c7, 1449177b87f768353909e930a99b902675119b2b +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e5811b8c09df9bc80eabc95339fceded23f16289, < d930276f2cddd0b7294cac7a8fe7b877f6d9e08d
Fixed in
  • d930276f2cddd0b7294cac7a8fe7b877f6d9e08d
LinuxLinuxAffected
  • ≥ e5811b8c09df9bc80eabc95339fceded23f16289, < 3884976f87448e269908ae61bd5d62d54ce9c0c7
Fixed in
  • 3884976f87448e269908ae61bd5d62d54ce9c0c7
LinuxLinuxAffected
  • ≥ e5811b8c09df9bc80eabc95339fceded23f16289, < 1449177b87f768353909e930a99b902675119b2b
Fixed in
  • 1449177b87f768353909e930a99b902675119b2b
LinuxLinuxAffected
  • ≥ e5811b8c09df9bc80eabc95339fceded23f16289, < 580844a9683afe7974856dd5b7886447435b3474
Fixed in
  • 580844a9683afe7974856dd5b7886447435b3474
LinuxLinuxAffected
  • ≥ e5811b8c09df9bc80eabc95339fceded23f16289, < 964b1c3eb71afe58bb61c8b984164447e000ae8a
Fixed in
  • 964b1c3eb71afe58bb61c8b984164447e000ae8a
LinuxLinuxAffected
  • ≥ e5811b8c09df9bc80eabc95339fceded23f16289, < 59c5a3e69c7630a811565937e64be70b08436761
Fixed in
  • 59c5a3e69c7630a811565937e64be70b08436761

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.

References

Community reviews

Loading reviews…