Answer in brief
CVE-2026-97411 records a Unknown severity vulnerability in net: ibm: emac: mal: fix potential system hang in mal_remove(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f6c1aad9b35fa083f48ce0c5926204891d82e089 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c4cb9a728df66c46067b26263f5beb633aae4087 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7c5d41f87f079990bf241359e3c1332d8d10fe87 || >=0 <6.12.111 || >=0 <6.18.53 | f6c1aad9b35fa083f48ce0c5926204891d82e089, c4cb9a728df66c46067b26263f5beb633aae4087, 7c5d41f87f079990bf241359e3c1332d8d10fe87, 6.12.111, 6.18.53 |
Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
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).
Quoted source text, attributed separately from HOL analysis.