Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90397

firmware: qcom: scm: Fix NULL dereference in IRQ handler before __scm is published

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 34 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 6bf32599223634294cdc6efb359ffaab1d68073c – < c9c1e3da0a206270e5df470ca1c82de52190d68c
    • affected 6bf32599223634294cdc6efb359ffaab1d68073c – < b451f38cb7f5bca78484362347f039c08c94de95
    • affected 6bf32599223634294cdc6efb359ffaab1d68073c – < 1d753df5899ec356272d08bc4718e82844e4bdf0
    • affected 6bf32599223634294cdc6efb359ffaab1d68073c – < f312ef5026678f14caf1378c5f7fffdf667f9c81
    • affected 6bf32599223634294cdc6efb359ffaab1d68073c – < 966d23c7e68ea32679275a7e3d2383181002c868
  • Linux · Linux

    • affected 6.3
    • unaffected < 6.3
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90397 badge
[![CVE-2026-90397](https://cveledger.app/badge/CVE-2026-90397.svg)](https://cveledger.app/cve/CVE-2026-90397)

Record last updated .