🛡️ CVE-2024-42319 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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

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().

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2024-42319 is recorded against 2 packages.

  • kernel (from 6.7.0 up to 6.10.3)
  • linux-kernel (from 6.7 up to 6.10.3)

Timeline and source

Published on 17 August 2024 and last revised on 15 July 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
lists.debian.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2024-42319 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-08-17
Updated 2026-08-12
Modified 2026-07-15

Affected Packages

Software From version Fixed in
kernel 6.7.0 6.10.3
linux-kernel 6.7 6.10.3

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2024-42319 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.