Answer in brief
CVE-2026-98904 records a Unknown severity vulnerability in mailbox: imx: Use devm_pm_runtime_enable(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b30a047744ea4344bb6f854b0a052cf276349128 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <adcaa21d50c3a4c884f4d0b7a95fa3bd7a07cf84 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1f602619e408b6e9655ee76656a2a5ab6e89c5e4 || >=0 <6.12.111 || >=0 <6.18.53 | b30a047744ea4344bb6f854b0a052cf276349128, adcaa21d50c3a4c884f4d0b7a95fa3bd7a07cf84, 1f602619e408b6e9655ee76656a2a5ab6e89c5e4, 6.12.111, 6.18.53 |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
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().
Quoted source text, attributed separately from HOL analysis.