VulnerabilityPublished 17 Sep 2026Updated 21 Oct 2026

CVE-2026-90397: Linux kernel · firmware: qcom: scm: Fix NULL dereference in IRQ handler before __scm is published

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in f312ef5026678f14caf1378c5f7fffdf667f9c81 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:30 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in f312ef5026678f14caf1378c5f7fffdf667f9c81, c9c1e3da0a206270e5df470ca1c82de52190d68c, b451f38cb7f5bca78484362347f039c08c94de95 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 6bf32599223634294cdc6efb359ffaab1d68073c, < f312ef5026678f14caf1378c5f7fffdf667f9c81	Fixed in f312ef5026678f14caf1378c5f7fffdf667f9c81
LinuxLinux	Affected ≥ 6bf32599223634294cdc6efb359ffaab1d68073c, < c9c1e3da0a206270e5df470ca1c82de52190d68c	Fixed in c9c1e3da0a206270e5df470ca1c82de52190d68c
LinuxLinux	Affected ≥ 6bf32599223634294cdc6efb359ffaab1d68073c, < b451f38cb7f5bca78484362347f039c08c94de95	Fixed in b451f38cb7f5bca78484362347f039c08c94de95
LinuxLinux	Affected ≥ 6bf32599223634294cdc6efb359ffaab1d68073c, < 966d23c7e68ea32679275a7e3d2383181002c868	Fixed in 966d23c7e68ea32679275a7e3d2383181002c868
LinuxLinux	Affected ≥ 6bf32599223634294cdc6efb359ffaab1d68073c, < 1d753df5899ec356272d08bc4718e82844e4bdf0	Fixed in 1d753df5899ec356272d08bc4718e82844e4bdf0
LinuxLinux	Affected =6.3	Fixed in–

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.

References

Community reviews

Loading reviews…