{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90397 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90397 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90397 and fix it if it is affected.\n\nWhat it is: CVE-2026-90397 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90397 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90397/ (Markdown: https://insights.sbomify.com/CVE-2026-90397/index.md)","id":"CVE-2026-90397","markdown":"https://insights.sbomify.com/CVE-2026-90397/index.md","name":"CVE-2026-90397","record":{"aliases":["AZL-101921","BELL-CVE-2026-90397","DEBIAN-CVE-2026-90397","GHSA-gcqw-f4ff-hx84","UBUNTU-CVE-2026-90397"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A race condition in the Qualcomm SCM driver causes a NULL pointer dereference during probe, leading to a kernel crash and denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"firmware: qcom: scm: Fix NULL dereference in IRQ handler before __scm is published","id":"CVE-2026-90397","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"wifi: ath11k: fix stride mismatch in mac_phy_caps_parse()","id":"CVE-2026-90398"},"packages":[],"prev":{"headline":"block: fix dio leak on metadata mapping error","id":"CVE-2026-90396"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A race condition in the Qualcomm SCM driver causes a NULL pointer dereference during probe, leading to a kernel crash and denial of service.","url":"https://insights.sbomify.com/CVE-2026-90397/"}