Bug 2540547 (CVE-2026-97411) - CVE-2026-97411 kernel: net: ibm: emac: mal: fix potential system hang in mal_remove()
Summary: CVE-2026-97411 kernel: net: ibm: emac: mal: fix potential system hang in mal_...
Keywords:
Status: NEW
Alias: CVE-2026-97411
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-24 17:11 UTC by OSIDB Bzimport
Modified: 2026-09-29 10:13 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-24 17:11:28 UTC
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).


Note You need to log in before you can comment on or make changes to this bug.