{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90180 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90180 is a 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-90180 and fix it if it is affected.\n\nWhat it is: CVE-2026-90180 is a 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-90180 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-90180/ (Markdown: https://insights.sbomify.com/CVE-2026-90180/index.md)","id":"CVE-2026-90180","markdown":"https://insights.sbomify.com/CVE-2026-90180/index.md","name":"CVE-2026-90180","record":{"aliases":["AZL-102269","BELL-CVE-2026-90180","DEBIAN-CVE-2026-90180","GHSA-h84p-58mj-wq53","UBUNTU-CVE-2026-90180"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A race condition in the mtip32xx block driver allows local attackers to trigger a use-after-free during device removal, potentially causing system crashes or code execution.","user_interaction":"not_required","vuln_class":"race_condition"},"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\nblock: mtip32xx: synchronize ioctls with device removal\n\nThe ioctl handlers only test REMOVE_PENDING before entering\nmtip_hw_ioctl(). Removal can set that bit immediately afterwards and free\ndd-\u003eport in mtip_hw_exit() while an ioctl still dereferences it. An already\nopen block device can reach the handlers while del_gendisk() is in\nprogress.\n\nSerialize both native and compat ioctls with removal. Set REMOVE_PENDING\nbefore taking the mutex so new callers fail after an in-flight ioctl has\ndrained, and hold the mutex until the port has been torn down.","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":"block: mtip32xx: synchronize ioctls with device removal","id":"CVE-2026-90180","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"ublk: avoid teardown retry loop on xarray allocation failure","id":"CVE-2026-90181"},"packages":[],"prev":{"headline":"apparmor: fix deadlock in complain-mode change_hat","id":"CVE-2026-90179"},"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 mtip32xx block driver allows local attackers to trigger a use-after-free during device removal, potentially causing system crashes or code execution.","url":"https://insights.sbomify.com/CVE-2026-90180/"}