Skip to content
Threat Brief

← All advisories

CVE-2026-90193

Severity unknownNo known exploitationFix available

mailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 11% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In the Linux kernel, the following vulnerability has been resolved: mailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler qcom_cpucp_mbox_irq_fn() calls mbox_chan_received_data() while holding chan->lock. Under PREEMPT_RT, spin_lock_irqsave() is converted to an rt_spinlock (rtmutex-based), which tracks ownership and can sleep. The callback chain triggered by mbox_chan_received_data() eventually reaches mailbox_clear_channel() -> mbox_send_message() -> add_to_rbuf(), which attempts to re-acquire the same chan->lock. Since rtmutex detects the re-entrant lock attempt by the same owner, the thread blocks waiting for a lock it already holds, causing a permanent deadlock. This deadlock manifests as 'irq/N-apss_cpucp_mbox' stuck in D state with the following call trace: rt_spin_lock -> mbox_send_message -> mailbox_clear_channel -> scmi_rx_callback -> mbox_chan_received_data [ lock here] Fix by saving chan->cl locally and clearing the HW interrupt register inside the lock, then invoking mbox_chan_received_data() after releasing the lock. This preserves the mutual exclusion for chan->cl access while avoiding the lock re-entrancy that causes the PREEMPT_RT deadlock.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 0e2a9a03106cd5fa0dbc9047675e7645c55e2669 before aa482273f32117c3adeba9b1cc945e0b5d33722daa482273f32117c3adeba9b1cc945e0b5d33722dCVE Program
LinuxLinuxfrom 0e2a9a03106cd5fa0dbc9047675e7645c55e2669 before 8b8de6400c86937ed57d680d06d716e167b381de8b8de6400c86937ed57d680d06d716e167b381deCVE Program
LinuxLinuxfrom 0e2a9a03106cd5fa0dbc9047675e7645c55e2669 before e40b3edeaf25cd09e9c88edb1ef99373ca37593be40b3edeaf25cd09e9c88edb1ef99373ca37593bCVE Program
LinuxLinuxfrom 0e2a9a03106cd5fa0dbc9047675e7645c55e2669 before 3690aaa6d18f6775c3e7932fb8af8c5bf6a6b69c3690aaa6d18f6775c3e7932fb8af8c5bf6a6b69cCVE Program
LinuxLinux6.11Not documentedCVE Program
Microsoftazl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0Not documented0:6.18.57-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 6.12.110 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.52 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.6 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.11Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references