FKIE_CVE-2026-90397

Vulnerability from fkie_nvd - Published: 2026-09-17 17:17 - Updated: 2026-09-17 17:17
Severity
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.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/1d753df5899ec356272d08bc4718e82844e4bdf0
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/966d23c7e68ea32679275a7e3d2383181002c868
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/b451f38cb7f5bca78484362347f039c08c94de95
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/f312ef5026678f14caf1378c5f7fffdf667f9c81
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/firmware/qcom/qcom_scm-smc.c",
            "drivers/firmware/qcom/qcom_scm.c",
            "drivers/firmware/qcom/qcom_scm.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "b451f38cb7f5bca78484362347f039c08c94de95",
              "status": "affected",
              "version": "6bf32599223634294cdc6efb359ffaab1d68073c",
              "versionType": "git"
            },
            {
              "lessThan": "1d753df5899ec356272d08bc4718e82844e4bdf0",
              "status": "affected",
              "version": "6bf32599223634294cdc6efb359ffaab1d68073c",
              "versionType": "git"
            },
            {
              "lessThan": "f312ef5026678f14caf1378c5f7fffdf667f9c81",
              "status": "affected",
              "version": "6bf32599223634294cdc6efb359ffaab1d68073c",
              "versionType": "git"
            },
            {
              "lessThan": "966d23c7e68ea32679275a7e3d2383181002c868",
              "status": "affected",
              "version": "6bf32599223634294cdc6efb359ffaab1d68073c",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/firmware/qcom/qcom_scm-smc.c",
            "drivers/firmware/qcom/qcom_scm.c",
            "drivers/firmware/qcom/qcom_scm.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.3"
            },
            {
              "lessThan": "6.3",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.110",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.52",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: qcom: scm: Fix NULL dereference in IRQ handler before __scm is published\n\nIn qcom_scm_probe(), devm_request_threaded_irq() is called before\nsmp_store_release(\u0026__scm, scm). Two paths can dereference __scm before\nit is published, both causing a NULL pointer dereference.\n\nThe IRQ handler receives scm via its data argument but passes only wq_ctx\nto qcom_scm_waitq_wakeup() and qcom_scm_get_completion(), which then\ndereference __scm directly. Thread scm through both functions so the IRQ\nhandler path never touches __scm.\n\nNon-atomic SMC calls made during probe (e.g. from qcom_tzmem_init via\nqcom_scm_shm_bridge_enable) can return WAITQ_SLEEP, causing\nqcom_scm_wait_for_wq_completion() to run before __scm is published and\ndereference it. Add platform_set_drvdata(pdev, scm) early in probe and\nchange qcom_scm_wait_for_wq_completion() to take the device pointer and\nuse dev_get_drvdata() to reach scm, removing any dependency on __scm."
    }
  ],
  "id": "CVE-2026-90397",
  "lastModified": "2026-09-17T17:17:39.417",
  "metrics": {},
  "published": "2026-09-17T17:17:39.417",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/1d753df5899ec356272d08bc4718e82844e4bdf0"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/966d23c7e68ea32679275a7e3d2383181002c868"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/b451f38cb7f5bca78484362347f039c08c94de95"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/f312ef5026678f14caf1378c5f7fffdf667f9c81"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.