{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90402 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90402 is a high-severity 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-90402 and fix it if it is affected.\n\nWhat it is: CVE-2026-90402 is a high-severity 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-90402 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-90402/ (Markdown: https://insights.sbomify.com/CVE-2026-90402/index.md)","id":"CVE-2026-90402","markdown":"https://insights.sbomify.com/CVE-2026-90402/index.md","name":"CVE-2026-90402","record":{"aliases":["BELL-CVE-2026-90402","DEBIAN-CVE-2026-90402","GHSA-fqr5-r6rr-x7fx","UBUNTU-CVE-2026-90402"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel MHI driver","requires_auth":"low_privilege","summary":"Improper cleanup in the Linux kernel MHI host driver when sysfs creation fails, potentially leaving a registered device in an inconsistent state.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbus: mhi: host: Fix controller cleanup on EDL sysfs failure\n\nmhi_register_controller() adds the controller device before creating the\noptional trigger_edl sysfs file. If sysfs_create_file() fails, the error\npath only drops the device reference and leaves the device registered.\n\nHence, call device_del() in the error path before put_device().","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":"bus: mhi: host: Fix controller cleanup on EDL sysfs failure","id":"CVE-2026-90402","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"wifi: rtlwifi: pci: fix error path in rtl_pci_probe()","id":"CVE-2026-90403"},"packages":[],"prev":{"headline":"md: remove REQ_NOWAIT support from raid1/10/456","id":"CVE-2026-90401"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"Improper cleanup in the Linux kernel MHI host driver when sysfs creation fails, potentially leaving a registered device in an inconsistent state.","url":"https://insights.sbomify.com/CVE-2026-90402/"}