CVE-2026-97411

Unknown

Last modified

CVE-2026-97411 is a vulnerability of currently unknown severity. 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.

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).

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= b3e441c6ed8655a42e7b4da1b6dc7939f259d9c9, < f6c1aad9b35fa083f48ce0c5926204891d82e089; >= b3e441c6ed8655a42e7b4da1b6dc7939f259d9c9, < c4cb9a728df66c46067b26263f5beb633aae4087; >= b3e441c6ed8655a42e7b4da1b6dc7939f259d9c9, < 7c5d41f87f079990bf241359e3c1332d8d10fe87
LinuxLinux2.6.24

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-97411?
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).
How severe is CVE-2026-97411?
Severity scoring for CVE-2026-97411 is pending analysis.
How do I fix CVE-2026-97411?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-97411?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST