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-97411net: ibm: emac: mal: fix potential system hang in mal_remove()

Description

In the Linux kernel, the following vulnerability has been resolved: net: ibm: emac: mal: fix potential system hang in mal_remove() napi_disable() is not idempotent and calling it on an already-disabled or unenabled NAPI context will cause the kernel to spin indefinitely waiting for the NAPI_STATE_SCHED bit to clear. In mal_remove(), napi_disable() is called unconditionally. If no MACs were registered, NAPI was never enabled. Also, if they were registered but subsequently unregistered, NAPI was already disabled in mal_unregister_commac(). In either case, calling napi_disable() causes the kernel to hang upon module removal. Fix this by only calling napi_disable() in mal_remove() if the commac list is not empty (which implies NAPI is enabled).

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 (17 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 b3e441c6ed8655a42e7b4da1b6dc7939f259d9c9 – < 9c1c814a662d9c81959eba591bb52b24639390f2
    • affected b3e441c6ed8655a42e7b4da1b6dc7939f259d9c9 – < 34c4cae51718d6f393415e01c61314c1bde02f2e
    • affected b3e441c6ed8655a42e7b4da1b6dc7939f259d9c9 – < 62126e73e230cf4bd6c27cf201949c4290af84a1
    • affected b3e441c6ed8655a42e7b4da1b6dc7939f259d9c9 – < f0399b3e212741bc5a64b8399d6266c4a150bdfe
    • affected b3e441c6ed8655a42e7b4da1b6dc7939f259d9c9 – < f6c1aad9b35fa083f48ce0c5926204891d82e089
    • affected b3e441c6ed8655a42e7b4da1b6dc7939f259d9c9 – < c4cb9a728df66c46067b26263f5beb633aae4087
    • affected b3e441c6ed8655a42e7b4da1b6dc7939f259d9c9 – < 7c5d41f87f079990bf241359e3c1332d8d10fe87
  • Linux · Linux

    • affected 2.6.24
    • unaffected < 2.6.24
    • unaffected 5.10.271 – ≤ 5.10.*
    • 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

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .