firmware: arm_scmi: Quiesce notifications before teardown
In 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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.12.110, 6.18.52, 7.2.6
- CVEs
- CVE-2026-93091
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 15:36 UTC · Revision 1
Source evidence
firmware: arm_scmi: Quiesce notifications before teardown
core-osv · Original sourcePublished 17 Sept 2026, 16:11 UTC
In 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.
osv:CVE-2026-93091
Kernel
Fixed versions: 6.12.110, 6.18.52, 7.2.6
Complete source record
{
"id": "ae0214d637d075c1ee76aea718e3dc05b40ab4ea54e12500d739a567ee8843c3",
"url": "https://osv.dev/vulnerability/CVE-2026-93091",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "firmware: arm_scmi: Quiesce notifications before teardown",
"summary": "In 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.",
"evidence": "osv:CVE-2026-93091",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.12.110",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.52",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.6",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-93091",
"aliases": [
"CVE-2026-93091"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "1e7cbfaa66d39e78bd24df0c78b55df68176b59e"
},
{
"fixed": "6778bcabd2e0c32f73476f0bc6369013692540be"
},
{
"fixed": "2aac23bc0a79af41104d99823bb250fae92ba144"
},
{
"fixed": "5e30d3d16d1a9e599be4dcea872874e65e2c277b"
},
{
"fixed": "8e49055d0d495c9c07575ad8e111d9eaf0efb13f"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-93091.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.15.0"
},
{
"fixed": "6.12.110"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.52"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-93091.json"
}
}
],
"modified": "2026-10-28T02:30:29.968230267Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/2aac23bc0a79af41104d99823bb250fae92ba144",
"https://git.kernel.org/stable/c/5e30d3d16d1a9e599be4dcea872874e65e2c277b",
"https://git.kernel.org/stable/c/6778bcabd2e0c32f73476f0bc6369013692540be",
"https://git.kernel.org/stable/c/8e49055d0d495c9c07575ad8e111d9eaf0efb13f",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/93xxx/CVE-2026-93091.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-93091",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/93xxx/CVE-2026-93091.json"
}
},
"related_cves": [
{
"value": "CVE-2026-93091",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 496878,
"published_at": "2026-09-17T16:11:07.055+00:00"
}