CVE-2024-42319mailbox: mtk-cmdq: Move devm_mbox_controller_register() after devm_pm_runtime_enable()
- 5.5MediumCVSS base score
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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().
Timeline
ID reserved
By Linux
- 18 days later
· 18 days later
Published
- 21 months later
· 21 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 623a6143a845bd485b00ba684f0ccef11835edab – < 1403991a40b94438a2acc749bf05c117abdb34f9
- affected 623a6143a845bd485b00ba684f0ccef11835edab – < d00df6700ad10974a7e20646956f4ff22cdbe0ec
- affected 623a6143a845bd485b00ba684f0ccef11835edab – < 11fa625b45faf0649118b9deaf2d31c86ac41911
- affected 623a6143a845bd485b00ba684f0ccef11835edab – < a8bd68e4329f9a0ad1b878733e0f80be6a971649
- affected 4.19
- unaffected < 4.19
- unaffected 6.1.120 – ≤ 6.1.*
- unaffected 6.6.64 – ≤ 6.6.*
- unaffected 6.10.3 – ≤ 6.10.*
- unaffected 6.11 – ≤ *
References
References5
- https://git.kernel.org/stable/c/1403991a40b94438a2acc749bf05c117abdb34f9 (opens in a new tab)
- https://git.kernel.org/stable/c/d00df6700ad10974a7e20646956f4ff22cdbe0ec (opens in a new tab)
- https://git.kernel.org/stable/c/11fa625b45faf0649118b9deaf2d31c86ac41911 (opens in a new tab)
- https://git.kernel.org/stable/c/a8bd68e4329f9a0ad1b878733e0f80be6a971649 (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-39547 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-42319)Record last updated .