Skip to main content
VulnerabilityPublished Updated

CVE-2024-42319: Linux kernel · mailbox: mtk-cmdq: Move devm_mbox_controller_register() after devm_pm_runtime_enable()

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 30 Oct 2026, 00:37 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Aug 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 29 Oct 2026.

What to do

AI-suggested

A fix is available by reordering the calls in the cmdq_probe() function to call devm_mbox_controller_register() after devm_pm_runtime_enable(). Users should apply the updated Linux kernel patches that address this issue. No other mitigations are indicated.

Description

CVE-2024-42319 is a medium-severity vulnerability in the Linux kernel's mtk-cmdq mailbox driver. The issue arises from the incorrect order of calls in the cmdq_probe() function, where devm_mbox_controller_register() is called before devm_pm_runtime_enable(). This leads to a WARN_ON message triggered by pm_runtime_get_sync() being called after pm_runtime_disable() during device unbinding, causing potential kernel warnings and instability.

References

Community reviews

Loading reviews…