CVE-2024-42319

published 17 Aug 2024 · updated 11 May 2026

mailbox: mtk-cmdq: Move devm_mbox_controller_register() after devm_pm_runtime_enable()

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 11fa625b45faf0649118b9deaf2d31c86ac41911, Kernel 1403991a40b94438a2acc749bf05c117abdb34f9, Kernel a8bd68e4329f9a0ad1b878733e0f80be6a971649 and 1 more.

In the Linux kernel, the following vulnerability has been resolved: mailbox: mtk-cmdq: Move devm_mbox_controller_register() after devm_pm_runtime_enable() When mtk-cmdq unbinds, a WARN_ON message with condition pm_runtime_get_sync() < 0 occurs. According to the call tracei below: cmdq_mbox_shutdown mbox_free_channel mbox_controller_unregister __devm_mbox_controller_unregister ... The root cause can be deduced to be calling pm_runtime_get_sync() after calling pm_runtime_disable() as observed below: 1. CMDQ driver uses devm_mbox_controller_register() in cmdq_probe() to bind the cmdq device to the mbox_controller, so devm_mbox_controller_unregister() will automatically unregister the device bound to the mailbox controller when the device-managed resource is removed. That means devm_mbox_controller_unregister() and cmdq_mbox_shoutdown() will be called after cmdq_remove(). 2. CMDQ driver also uses devm_pm_runtime_enable() in cmdq_probe() after devm_mbox_controller_register(), so that devm_pm_runtime_disable() will be called after cmdq_remove(), but before devm_mbox_controller_unregister(). To fix this problem, cmdq_probe() needs to move devm_mbox_controller_register() after devm_pm_runtime_enable() to make devm_pm_runtime_disable() be called after devm_mbox_controller_unregister().

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=4.19, >=623a6143a845bd485b00ba684f0ccef11835edab <11fa625b45faf0649118b9deaf2d31c86ac41911, >=623a6143a845bd485b00ba684f0ccef11835edab <1403991a40b94438a2acc749bf05c117abdb34f9, >=623a6143a845bd485b00ba684f0ccef11835edab <a8bd68e4329f9a0ad1b878733e0f80be6a971649, >=623a6143a845bd485b00ba684f0ccef11835edab <d00df6700ad10974a7e20646956f4ff22cdbe0ec11fa625b45faf0649118b9deaf2d31c86ac41911, 1403991a40b94438a2acc749bf05c117abdb34f9, a8bd68e4329f9a0ad1b878733e0f80be6a971649, d00df6700ad10974a7e20646956f4ff22cdbe0ec

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2024-42319 severity on Zeptric[![CVE-2024-42319](https://zeptric.io/badge/cve/CVE-2024-42319.svg)](https://zeptric.io/cve/CVE-2024-42319)