GHSA-WCG4-82X5-PPXC
Vulnerability from github – Published: 2026-09-24 18:31 – Updated: 2026-09-24 18:31In 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": [],
"aliases": [
"CVE-2026-97411"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-24T17:17:18Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ibm: emac: mal: fix potential system hang in mal_remove()\n\nnapi_disable() is not idempotent and calling it on an already-disabled\nor unenabled NAPI context will cause the kernel to spin indefinitely\nwaiting for the NAPI_STATE_SCHED bit to clear.\n\nIn mal_remove(), napi_disable() is called unconditionally. If no MACs were\nregistered, NAPI was never enabled. Also, if they were registered but\nsubsequently unregistered, NAPI was already disabled in\nmal_unregister_commac(). In either case, calling napi_disable() causes\nthe kernel to hang upon module removal.\n\nFix this by only calling napi_disable() in mal_remove() if the commac list\nis not empty (which implies NAPI is enabled).",
"id": "GHSA-wcg4-82x5-ppxc",
"modified": "2026-09-24T18:31:31Z",
"published": "2026-09-24T18:31:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97411"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7c5d41f87f079990bf241359e3c1332d8d10fe87"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c4cb9a728df66c46067b26263f5beb633aae4087"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f6c1aad9b35fa083f48ce0c5926204891d82e089"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.