{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98904 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-98904 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-98904 and fix it if it is affected.\n\nWhat it is: CVE-2026-98904 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-98904 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98904/ (Markdown: https://insights.sbomify.com/CVE-2026-98904/index.md)","id":"CVE-2026-98904","markdown":"https://insights.sbomify.com/CVE-2026-98904/index.md","name":"CVE-2026-98904","record":{"aliases":["AZL-110579","BELL-CVE-2026-98904","DEBIAN-CVE-2026-98904","GHSA-6qfv-c5c2-gj3p","UBUNTU-CVE-2026-98904"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmailbox: imx: Use devm_pm_runtime_enable()\n\nsashiko complained about early usage of the device while probe isn't\ncompleted. This can be mitigated by delaying the pm_runtime_enable()\ninto the removal path instead doing it early. This ensures that in an\nerror case the device is removed (and imx_mu_shutdown()) before\npm_runtime_disable() so we don't have to do this manually.\n\nFor the order to work, lets move devm_mbox_controller_register() until\nafter the pm-runtime part. So the reverse order will be mbox-controller\nremoval followed by disabling pm runtime.\n\nUse devm_pm_runtime_enable(), remove manual pm_runtime_disable()\ninvocations and move the pm_runtime handling in probe before\ndevm_mbox_controller_register().","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"mailbox: imx: Use devm_pm_runtime_enable()","id":"CVE-2026-98904","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"drm/amdkfd: Properly acquire queue buffers in CRIU restore","id":"CVE-2026-98905"},"packages":[],"prev":{"headline":"mailbox: imx: Add a channel shutdown field","id":"CVE-2026-98903"},"products":["Linux"],"published":"2026-10-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-26","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-98904/"}