CVE-2026-98904None▾ Sunlit

mailbox: imx: Use devm_pm_runtime_enable()

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_run…

▾ Sunlit zone — Low / medium · no exploitation signal

Depth score3/ 100 · Minimal

impact 2.8 · likelihood 0 · exploitation 0

⚡ Agent-ready:Raw markdown ↗JSON ↗

Proof of concept

Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.

…

Published

Oct 23, 2026

Updated

Oct 26, 2026

CVSS

—

Vendor

Linux

Product

Linux

CWE

—

Depth score

3 · Minimal

EPSS

0.17% · p7

Platforms

—

Source

CVEORG

Vector

—

EPSS history

Exploit-prediction probability, daily snapshots since Oct 25.

0.2% → 0.2%

Timeline

Disclosure to exploitation, from the record and what we observed since indexing it.

3 events · 3 days

Oct 23, 2026Published
Disclosed via CVEORG
Oct 25, 2026EPSS first tracked
0.2%
Oct 26, 2026Record revised
Last analysed / modified upstream

Linux #cve.org

Affected

Linux >= 676f23eab75adbf72c029bdfb7b5a7b2f1129177 < b30a047744ea4344bb6f854b0a052cf276349128
Linux >= 676f23eab75adbf72c029bdfb7b5a7b2f1129177 < adcaa21d50c3a4c884f4d0b7a95fa3bd7a07cf84
Linux >= 676f23eab75adbf72c029bdfb7b5a7b2f1129177 < 1f602619e408b6e9655ee76656a2a5ab6e89c5e4
Linux 5.8

Full technical detail▾

Overview

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

Affected

Linux >= 676f23eab75adbf72c029bdfb7b5a7b2f1129177 < b30a047744ea4344bb6f854b0a052cf276349128
Linux >= 676f23eab75adbf72c029bdfb7b5a7b2f1129177 < adcaa21d50c3a4c884f4d0b7a95fa3bd7a07cf84
Linux >= 676f23eab75adbf72c029bdfb7b5a7b2f1129177 < 1f602619e408b6e9655ee76656a2a5ab6e89c5e4
Linux 5.8

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

References

Related vulnerabilities

Connected by shared product, vendor, weakness, or advisory.

#cve.org

mailbox: imx: Use devm_pm_runtime_enable()

▾ Sunlit zone — Low / medium · no exploitation signal

Depth score3/ 100 · Minimal

impact 2.8 · likelihood 0 · exploitation 0

Overview

In the Linux kernel, the following vulnerability has been resolved:

mailbox: imx: Use devm_pm_runtime_enable()

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