{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90216 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90216 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-90216 and fix it if it is affected.\n\nWhat it is: CVE-2026-90216 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-90216 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-90216/ (Markdown: https://insights.sbomify.com/CVE-2026-90216/index.md)","id":"CVE-2026-90216","markdown":"https://insights.sbomify.com/CVE-2026-90216/index.md","name":"CVE-2026-90216","record":{"aliases":["AZL-102449","BELL-CVE-2026-90216","DEBIAN-CVE-2026-90216","GHSA-98x6-774g-8659","UBUNTU-CVE-2026-90216"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel UBI","requires_auth":"high_privilege","summary":"A logic error in Linux kernel UBI initialization rollback can cause resource leaks or instability when explicit device numbers are used, requiring local privileged access.","user_interaction":"not_required","vuln_class":"other"},"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\nubi: Fix rollback for explicit UBI device numbers\n\nubi_init_attach() rolls back module initialization failures by scanning\nubi_devices[0..i-1], where i is the mtd= parameter index. That assumes\nthe parameter index matches the UBI device number.\n\nThat assumption is not true when mtd= specifies an explicit ubi_num. A\nsuccessfully attached device can be stored at a higher ubi_devices[]\nslot, and a later failure can miss it during rollback.\n\nScan the full ubi_devices[] array and detach by the actual array index,\nmatching the way UBI devices are stored.","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":"ubi: Fix rollback for explicit UBI device numbers","id":"CVE-2026-90216","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"bpf: Compare iterator types during state pruning","id":"CVE-2026-90217"},"packages":[],"prev":{"headline":"mtd: ubi: Release device reference on busy detach","id":"CVE-2026-90215"},"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 logic error in Linux kernel UBI initialization rollback can cause resource leaks or instability when explicit device numbers are used, requiring local privileged access.","url":"https://insights.sbomify.com/CVE-2026-90216/"}