CVE-2026-90397
CVE CVE-2026-90397EUVD EUVD-2026-82058Published 2026-09-17T16:09:28.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 6bf32599223634294cdc6efb359ffaab1d68073c <f312ef5026678f14caf1378c5f7fffdf667f9c81; patch: 7.2.6; patch: 0; 6bf32599223634294cdc6efb359ffaab1d68073c <966d23c7e68ea32679275a7e3d2383181002c868; 6bf32599223634294cdc6efb359ffaab1d68073c <b451f38cb7f5bca78484362347f039c08c94de95; 6.3; 6bf32599223634294cdc6efb359ffaab1d68073c <1d753df5899ec356272d08bc4718e82844e4bdf0; patch: 7.3-rc1; patch: 6.12.110; patch: 6.18.52
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.