{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90193 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90193 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-90193 and fix it if it is affected.\n\nWhat it is: CVE-2026-90193 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-90193 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-90193/ (Markdown: https://insights.sbomify.com/CVE-2026-90193/index.md)","id":"CVE-2026-90193","markdown":"https://insights.sbomify.com/CVE-2026-90193/index.md","name":"CVE-2026-90193","record":{"aliases":["BELL-CVE-2026-90193","DEBIAN-CVE-2026-90193","GHSA-vrrh-vfw6-8f53","UBUNTU-CVE-2026-90193"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A self-deadlock in the Qualcomm CPUCP mailbox driver under PREEMPT_RT causes a permanent system hang, requiring a kernel patch.","user_interaction":"not_required","vuln_class":"race_condition"},"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\nmailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler\n\nqcom_cpucp_mbox_irq_fn() calls mbox_chan_received_data() while holding\nchan-\u003elock. Under PREEMPT_RT, spin_lock_irqsave() is converted to an\nrt_spinlock (rtmutex-based), which tracks ownership and can sleep.\n\nThe callback chain triggered by mbox_chan_received_data() eventually\nreaches mailbox_clear_channel() -\u003e mbox_send_message() -\u003e add_to_rbuf(),\nwhich attempts to re-acquire the same chan-\u003elock. Since rtmutex detects\nthe re-entrant lock attempt by the same owner, the thread blocks waiting\nfor a lock it already holds, causing a permanent deadlock.\n\nThis deadlock manifests as 'irq/N-apss_cpucp_mbox' stuck in D state\nwith the following call trace:\n  rt_spin_lock -\u003e mbox_send_message -\u003e mailbox_clear_channel -\u003e\n  scmi_rx_callback -\u003e mbox_chan_received_data [\u003c- held chan-\u003elock here]\n\nFix by saving chan-\u003ecl locally and clearing the HW interrupt register\ninside the lock, then invoking mbox_chan_received_data() after releasing\nthe lock. This preserves the mutual exclusion for chan-\u003ecl access while\navoiding the lock re-entrancy that causes the PREEMPT_RT deadlock.","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":"mailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler","id":"CVE-2026-90193","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"ACPI: scan: fix bus ID cleanup on device_add() failures","id":"CVE-2026-90194"},"packages":[],"prev":{"headline":"mailbox: qcom-cpucp: handle NULL data in send_data callback","id":"CVE-2026-90192"},"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-19","vendors":["Linux"]},"summary":"A self-deadlock in the Qualcomm CPUCP mailbox driver under PREEMPT_RT causes a permanent system hang, requiring a kernel patch.","url":"https://insights.sbomify.com/CVE-2026-90193/"}