firmware: qcom: scm: Fix NULL dereference in IRQ handler before __scm is published
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.110, 6.18.52, 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 6bf32599223634294cdc6efb359ffaab1d68073c · fixed in c9c1e3da0a206270e5df470ca1c82de52190d68c; From 6bf32599223634294cdc6efb359ffaab1d68073c · fixed in b451f38cb7f5bca78484362347f039c08c94de95; From 6bf32599223634294cdc6efb359ffaab1d68073c · fixed in 1d753df5899ec356272d08bc4718e82844e4bdf0; From 6bf32599223634294cdc6efb359ffaab1d68073c · fixed in f312ef5026678f14caf1378c5f7fffdf667f9c81; From 6bf32599223634294cdc6efb359ffaab1d68073c · fixed in 966d23c7e68ea32679275a7e3d2383181002c868
- Linux Linux
6.3
- KernelLinux
From 6.3.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6