GHSA-634X-XGVQ-4P3J
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
firmware: arm_scmi: Quiesce notifications before teardown
scmi_notification_exit() clears and releases the notification instance, but transport callbacks can still deliver incoming notifications until the TX/RX channels are freed. During remove, an RX interrupt in that window can enter scmi_notify() while notification state is being torn down and then dereference freed memory. The same ordering exists on the probe error path after notification initialization.
The notification late-init worker has a separate lifetime issue: protocol event registration queues ni->init_work on the system workqueue, so destroying ni->notify_wq does not drain that work. If the devres group is released while init_work is still pending or running, the late-init worker can dereference the freed notification instance.
Quiesce the notification core before TX/RX channels are torn down, then clean up the channels before releasing the notification core resources. Use disable_work_sync() so future late-init queueing is rejected and any already queued or running late-init work has completed before channel teardown starts.
{
"affected": [],
"aliases": [
"CVE-2026-93091"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:18:03Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scmi: Quiesce notifications before teardown\n\nscmi_notification_exit() clears and releases the notification instance,\nbut transport callbacks can still deliver incoming notifications until\nthe TX/RX channels are freed. During remove, an RX interrupt in that\nwindow can enter scmi_notify() while notification state is being torn\ndown and then dereference freed memory. The same ordering exists on the\nprobe error path after notification initialization.\n\nThe notification late-init worker has a separate lifetime issue: protocol\nevent registration queues ni-\u003einit_work on the system workqueue, so\ndestroying ni-\u003enotify_wq does not drain that work. If the devres group is\nreleased while init_work is still pending or running, the late-init worker\ncan dereference the freed notification instance.\n\nQuiesce the notification core before TX/RX channels are torn down, then\nclean up the channels before releasing the notification core resources.\nUse disable_work_sync() so future late-init queueing is rejected and any\nalready queued or running late-init work has completed before channel\nteardown starts.",
"id": "GHSA-634x-xgvq-4p3j",
"modified": "2026-09-17T18:32:09Z",
"published": "2026-09-17T18:32:09Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93091"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2aac23bc0a79af41104d99823bb250fae92ba144"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5e30d3d16d1a9e599be4dcea872874e65e2c277b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6778bcabd2e0c32f73476f0bc6369013692540be"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8e49055d0d495c9c07575ad8e111d9eaf0efb13f"
}
],
"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.