firmware: qcom: scm: Fix NULL dereference in IRQ handler before __scm is published
In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: scm: Fix NULL dereference in IRQ handler before __scm is published In qcom_scm_probe(), devm_request_threaded_irq() is called before smp_store_release(&__scm, scm). Two paths can dereference __scm before it is published, both causing a NULL pointer dereference. The IRQ handler receives scm via its data argument but passes only wq_ctx to qcom_scm_waitq_wakeup() and qcom_scm_get_completion(), which then dereference __scm directly. Thread scm through both functions so the IRQ handler path never touches __scm. Non-atomic SMC calls made during probe (e.g. from qcom_tzmem_init via qcom_scm_shm_bridge_enable) can return WAITQ_SLEEP, causing qcom_scm_wait_for_wq_completion() to run before __scm is published and dereference it. Add platform_set_drvdata(pdev, scm) early in probe and change qcom_scm_wait_for_wq_completion() to take the device pointer and use dev_get_drvdata() to reach scm, removing any dependency on __scm.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.12.110, 6.18.52, 6.6.160, 7.2.6
- CVEs
- CVE-2026-90397
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 02:36 UTC · Revision 1
Source evidence
firmware: qcom: scm: Fix NULL dereference in IRQ handler before __scm is published
core-osv · Original sourcePublished 17 Sept 2026, 16:09 UTC
In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: scm: Fix NULL dereference in IRQ handler before __scm is published In qcom_scm_probe(), devm_request_threaded_irq() is called before smp_store_release(&__scm, scm). Two paths can dereference __scm before it is published, both causing a NULL pointer dereference. The IRQ handler receives scm via its data argument but passes only wq_ctx to qcom_scm_waitq_wakeup() and qcom_scm_get_completion(), which then dereference __scm directly. Thread scm through both functions so the IRQ handler path never touches __scm. Non-atomic SMC calls made during probe (e.g. from qcom_tzmem_init via qcom_scm_shm_bridge_enable) can return WAITQ_SLEEP, causing qcom_scm_wait_for_wq_completion() to run before __scm is published and dereference it. Add platform_set_drvdata(pdev, scm) early in probe and change qcom_scm_wait_for_wq_completion() to take the device pointer and use dev_get_drvdata() to reach scm, removing any dependency on __scm.
osv:CVE-2026-90397
Kernel
Fixed versions: 6.6.160, 6.12.110, 6.18.52, 7.2.6
Complete source record
{
"id": "1077dc8eb3be1a51da40258e1912e4828b07324a80b39dee7a3ce0c30355c16e",
"url": "https://osv.dev/vulnerability/CVE-2026-90397",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "firmware: qcom: scm: Fix NULL dereference in IRQ handler before __scm is published",
"summary": "In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: scm: Fix NULL dereference in IRQ handler before __scm is published In qcom_scm_probe(), devm_request_threaded_irq() is called before smp_store_release(&__scm, scm). Two paths can dereference __scm before it is published, both causing a NULL pointer dereference. The IRQ handler receives scm via its data argument but passes only wq_ctx to qcom_scm_waitq_wakeup() and qcom_scm_get_completion(), which then dereference __scm directly. Thread scm through both functions so the IRQ handler path never touches __scm. Non-atomic SMC calls made during probe (e.g. from qcom_tzmem_init via qcom_scm_shm_bridge_enable) can return WAITQ_SLEEP, causing qcom_scm_wait_for_wq_completion() to run before __scm is published and dereference it. Add platform_set_drvdata(pdev, scm) early in probe and change qcom_scm_wait_for_wq_completion() to take the device pointer and use dev_get_drvdata() to reach scm, removing any dependency on __scm.",
"evidence": "osv:CVE-2026-90397",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.6.160",
"evidence": "/affected/1/ranges"
},
{
"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-90397",
"aliases": [
"CVE-2026-90397"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "6bf32599223634294cdc6efb359ffaab1d68073c"
},
{
"fixed": "c9c1e3da0a206270e5df470ca1c82de52190d68c"
},
{
"fixed": "b451f38cb7f5bca78484362347f039c08c94de95"
},
{
"fixed": "1d753df5899ec356272d08bc4718e82844e4bdf0"
},
{
"fixed": "f312ef5026678f14caf1378c5f7fffdf667f9c81"
},
{
"fixed": "966d23c7e68ea32679275a7e3d2383181002c868"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90397.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.3.0"
},
{
"fixed": "6.6.160"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.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-90397.json"
}
}
],
"modified": "2026-10-28T02:30:32.652748822Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/1d753df5899ec356272d08bc4718e82844e4bdf0",
"https://git.kernel.org/stable/c/966d23c7e68ea32679275a7e3d2383181002c868",
"https://git.kernel.org/stable/c/b451f38cb7f5bca78484362347f039c08c94de95",
"https://git.kernel.org/stable/c/c9c1e3da0a206270e5df470ca1c82de52190d68c",
"https://git.kernel.org/stable/c/f312ef5026678f14caf1378c5f7fffdf667f9c81",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90397.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-90397",
"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/90xxx/CVE-2026-90397.json"
}
},
"related_cves": [
{
"value": "CVE-2026-90397",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 499752,
"published_at": "2026-09-17T16:09:28.967+00:00"
}