Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-53177bnxt_en: Fix NULL pointer dereference

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.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53177, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected e5811b8c09df9bc80eabc95339fceded23f16289 – < 1449177b87f768353909e930a99b902675119b2b
    • affected e5811b8c09df9bc80eabc95339fceded23f16289 – < 964b1c3eb71afe58bb61c8b984164447e000ae8a
    • affected e5811b8c09df9bc80eabc95339fceded23f16289 – < 59c5a3e69c7630a811565937e64be70b08436761
    • affected e5811b8c09df9bc80eabc95339fceded23f16289 – < 1a418ad0e5e525d1d117dd1601681f75455af320
    • affected e5811b8c09df9bc80eabc95339fceded23f16289 – < 08e57d014ea19f303d5d57a849beb846f37788b7
    • affected e5811b8c09df9bc80eabc95339fceded23f16289 – < 3884976f87448e269908ae61bd5d62d54ce9c0c7
    • affected e5811b8c09df9bc80eabc95339fceded23f16289 – < 580844a9683afe7974856dd5b7886447435b3474
    • affected e5811b8c09df9bc80eabc95339fceded23f16289 – < d930276f2cddd0b7294cac7a8fe7b877f6d9e08d
  • Linux · Linux

    • affected 4.17
    • unaffected < 4.17
    • unaffected 5.10.260 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.94 – ≤ 6.12.*
    • unaffected 6.18.36 – ≤ 6.18.*
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53177 badge
[![CVE-2026-53177](https://cveledger.app/badge/CVE-2026-53177.svg)](https://cveledger.app/cve/CVE-2026-53177)

Record last updated .