# CVE-2026-98904: mailbox: imx: Use devm_pm_runtime_enable()


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-110579, BELL-CVE-2026-98904, DEBIAN-CVE-2026-98904, GHSA-6qfv-c5c2-gj3p, UBUNTU-CVE-2026-98904

## What is CVE-2026-98904?

CVE-2026-98904 is a vulnerability in Linux, published on 23 Oct 2026. 

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

## Which versions are affected by CVE-2026-98904?


## How do I fix CVE-2026-98904?

Upgrade to a fixed version.

## Is CVE-2026-98904 being exploited?

There is no known exploitation of CVE-2026-98904 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98904 and fix it if it is affected.

What it is: CVE-2026-98904 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98904 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98904/ (Markdown: https://insights.sbomify.com/CVE-2026-98904/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98904
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98904
- OSV: https://osv.dev/vulnerability/CVE-2026-98904

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98904/
Summaries are generated and may contain mistakes; the official description above is the record.