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-97434dpaa2-switch: fix handling of NAPI on the remove path

Description

In the Linux kernel, the following vulnerability has been resolved: dpaa2-switch: fix handling of NAPI on the remove path All the NAPI instances for a DPSW device are attached to the first switch port's net_device but shared by all ports. The NAPI instances get disabled only once the last port goes down. This causes an issue on the .remove() path where each port is unregistered and freed one at a time, causing the NAPI instances to be deleted even though they are not disabled. In order to avoid this, split up the unregister_netdev() calls from the free_netdev() so that we make sure all ports go down before we attempt a deletion of NAPI instances. Also, make the netif_napi_del() explicit as it is on the .probe() path.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 9 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 0b1b71370458860579831e77485883fcf2e8fbbe – < d39603e21087e9ef9cd125e5895cdc70b2eb154d
    • affected 0b1b71370458860579831e77485883fcf2e8fbbe – < bd16f46d0796109d241d6311a7577f9956467c96
    • affected 0b1b71370458860579831e77485883fcf2e8fbbe – < c996faba71fc465ad12c6d177bd1a9ad974f9ee8
    • affected 0b1b71370458860579831e77485883fcf2e8fbbe – < 569df157eb874cb3b50554d73b89f31599397b42
    • affected 0b1b71370458860579831e77485883fcf2e8fbbe – < 6518f87771c8833e587bd9881346fa759651c2ae
    • affected 0b1b71370458860579831e77485883fcf2e8fbbe – < e23d7c8c1d4ba435c457d7ffb2669175ec819b07
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .