https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 06:50:17 +0000 https://vulnerability.circl.lu/vuln/cve-2026-97411 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: ibm: emac: mal: fix potential system hang in mal_remove()</p> <p>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.</p> <p>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.</p> <p>Fix this by only calling napi_disable() in mal_remove() if the commac list is not empty (which implies NAPI is enabled).</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: ibm: emac: mal: fix potential system hang in mal_remove()</p> <p>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.</p> <p>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.</p> <p>Fix this by only calling napi_disable() in mal_remove() if the commac list is not empty (which implies NAPI is enabled).</p> https://vulnerability.circl.lu/vuln/cve-2026-97411