CVE-2026-90397

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

State
Published
Severity
Not scored
Published
Sep 17, 2026
Updated
Oct 21, 2026
Reserved
Sep 11, 2026

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 6bf32599223634294cdc6efb359ffaab1d68073c to before c9c1e3da0a206270e5df470ca1c82de52190d68cAffected
  • 6bf32599223634294cdc6efb359ffaab1d68073c to before b451f38cb7f5bca78484362347f039c08c94de95Affected
  • 6bf32599223634294cdc6efb359ffaab1d68073c to before 1d753df5899ec356272d08bc4718e82844e4bdf0Affected
  • 6bf32599223634294cdc6efb359ffaab1d68073c to before f312ef5026678f14caf1378c5f7fffdf667f9c81Affected
  • 6bf32599223634294cdc6efb359ffaab1d68073c to before 966d23c7e68ea32679275a7e3d2383181002c868Affected
LinuxLinux
  • 6.3Affected
  • before 6.3Not affected
  • 6.6.160 through 6.6.*Not affected
  • 6.12.110 through 6.12.*Not affected
  • 6.18.52 through 6.18.*Not affected
  • 7.2.6 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.