Answer in brief
CVE-2026-90397 records a Unknown severity vulnerability in firmware: qcom: scm: Fix NULL dereference in IRQ handler before __scm is published. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6bf32599223634294cdc6efb359ffaab1d68073c <b451f38cb7f5bca78484362347f039c08c94de95 || >=6bf32599223634294cdc6efb359ffaab1d68073c <1d753df5899ec356272d08bc4718e82844e4bdf0 || >=6bf32599223634294cdc6efb359ffaab1d68073c <f312ef5026678f14caf1378c5f7fffdf667f9c81 || >=6bf32599223634294cdc6efb359ffaab1d68073c <966d23c7e68ea32679275a7e3d2383181002c868 | b451f38cb7f5bca78484362347f039c08c94de95, 1d753df5899ec356272d08bc4718e82844e4bdf0, f312ef5026678f14caf1378c5f7fffdf667f9c81, 966d23c7e68ea32679275a7e3d2383181002c868 |
| Linux/Linuxgeneric | 6.3 | Not reported |
| Linux/Linuxgeneric | >=6bf32599223634294cdc6efb359ffaab1d68073c <c9c1e3da0a206270e5df470ca1c82de52190d68c || >=6bf32599223634294cdc6efb359ffaab1d68073c <b451f38cb7f5bca78484362347f039c08c94de95 || >=6bf32599223634294cdc6efb359ffaab1d68073c <1d753df5899ec356272d08bc4718e82844e4bdf0 || >=6bf32599223634294cdc6efb359ffaab1d68073c <f312ef5026678f14caf1378c5f7fffdf667f9c81 || >=6bf32599223634294cdc6efb359ffaab1d68073c <966d23c7e68ea32679275a7e3d2383181002c868 | c9c1e3da0a206270e5df470ca1c82de52190d68c, b451f38cb7f5bca78484362347f039c08c94de95, 1d753df5899ec356272d08bc4718e82844e4bdf0, f312ef5026678f14caf1378c5f7fffdf667f9c81, 966d23c7e68ea32679275a7e3d2383181002c868 |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.