All reports
Medium

kernel: mailbox: imx: Use devm_pm_runtime_enable()

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-98904

Probability of exploitation in the next 30 days: 0.17%

FIRST EPSS · 2026-11-19

Description

In the Linux kernel, the following vulnerability has been resolved: mailbox: imx: Use devm_pm_runtime_enable() sashiko complained about early usage of the device while probe isn't completed. This can be mitigated by delaying the pm_runtime_enable() into the removal path instead doing it early. This ensures that in an error case the device is removed (and imx_mu_shutdown()) before pm_runtime_disable() so we don't have to do this manually. For the order to work, lets move devm_mbox_controller_register() until after the pm-runtime part. So the reverse order will be mbox-controller removal followed by disabling pm runtime. Use devm_pm_runtime_enable(), remove manual pm_runtime_disable() invocations and move the pm_runtime handling in probe before devm_mbox_controller_register().

A flaw was found in the Linux kernel's i.MX mailbox driver. The driver prematurely registers the mailbox controller before completing runtime power management setup during device probing. A local user could exploit this race condition by interacting with the incompletely initialized device, potentially resulting in a system crash and Denial of Service (DoS).