{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90431 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90431 is an use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90431 and fix it if it is affected.\n\nWhat it is: CVE-2026-90431 is an use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90431 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-90431/ (Markdown: https://insights.sbomify.com/CVE-2026-90431/index.md)","id":"CVE-2026-90431","markdown":"https://insights.sbomify.com/CVE-2026-90431/index.md","name":"CVE-2026-90431","record":{"aliases":["AZL-102783","BELL-CVE-2026-90431","DEBIAN-CVE-2026-90431","GHSA-j445-23gj-v4rv","UBUNTU-CVE-2026-90431"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel remoteproc subsystem allows local attackers to trigger a use-after-free, potentially causing system crashes or privilege escalation.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","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\nremoteproc: Prevent crash handling to race with rproc_del()\n\nThere's no synchronization between rproc_crash_handler_work() and\nrproc_del(), as such it's possible for a driver to be removed while\ncrash-handler work is scheduled, or even executing - resulting in\nuse-after-free issues.\n\nTo avoid this the scheduled work need to be cancelled and synchronized\nagainst before the removal proceeds.\n\nIn order to ensure that this doesn't race with the reporting, and\nthereby scheduling new work, a \"deleting\" flag is introduced. This is\nsimilar to the RPROC_DELETE state that was introduced to ensure that\n\"start\" didn't race with rproc_del(), but the existing mechanism can not\nbe used as it's valid to call rproc_report_crash() in atomic context -\nand the \"state\" is protected by a mutex.\n\nIn the event that work is cancelled the pm_stay_awake() is left\nunbalanced and need to be unrolled.\n\nThe blocking and cancelling of crash-handler work prior to the actual\nrproc_shutdown() call does have the explicit side-effect that crashes\nresulting from the shutdown process will not enter the crash-handling\npath, and as such will not generate devcoredumps etc. Due to the\nexisting mutual exclusion between these code paths there's no concrete\nreduction in functionality, but further work would be needed to handle\nthis case.","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":"remoteproc: Prevent crash handling to race with rproc_del()","id":"CVE-2026-90431","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"sched_ext: Abort directly from the hardlockup handler","id":"CVE-2026-90432"},"packages":[],"prev":{"headline":"iommu/tegra241-cmdqv: Publish an LVCMDQ only after it is fully initialized","id":"CVE-2026-90430"},"products":["Linux"],"published":"2026-09-17","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-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel remoteproc subsystem allows local attackers to trigger a use-after-free, potentially causing system crashes or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-90431/"}