{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89450 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89450 is a high-severity vulnerability in Linux, published on 11 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-89450 and fix it if it is affected.\n\nWhat it is: CVE-2026-89450 is a high-severity vulnerability in Linux, published on 11 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-89450 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-89450/ (Markdown: https://insights.sbomify.com/CVE-2026-89450/index.md)","id":"CVE-2026-89450","markdown":"https://insights.sbomify.com/CVE-2026-89450/index.md","name":"CVE-2026-89450","record":{"aliases":["BELL-CVE-2026-89450","DEBIAN-CVE-2026-89450","GHSA-4jcm-3g5m-55hr","UBUNTU-CVE-2026-89450"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["privilege_escalation","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel IOMMU","requires_auth":"low_privilege","summary":"A guest VM can bypass IOMMU isolation by providing an oversized virtual Stream ID that aliases to a different device, potentially enabling privilege escalation.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommu/tegra241-cmdqv: Reject a vSID wider than the SID_MATCH field\n\ntegra241_vintf_init_vsid() programs the guest-provided vSID into SID_MATCH,\nwhose VIRT_SID field spans bits [20:1] with bit 0 as the match-enable flag.\nThe HW therefore matches only a 20-bit Stream ID.\n\nThe bound check rejects only virt_sid \u003e UINT_MAX, which admits a value far\nwider than the field. The write \"virt_sid \u003c\u003c 1 | 0x1\" then drops every bit\nabove 20: a virt_sid of 0x80000000 lands as SID_MATCH = 0x1, a valid match\non vSID 0, so the entry aliases the wrong Stream ID. Because vdev-\u003evirt_id\nis guest-controlled, a VMM can trigger it.\n\nValidate virt_sid against the field width with FIELD_MAX(), and program the\nregister with FIELD_PREP() so the value and the field stay consistent.","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":"iommu/tegra241-cmdqv: Reject a vSID wider than the SID_MATCH field","id":"CVE-2026-89450","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"iommu/sva: Set handle-\u003edev before the SVA handle is visible","id":"CVE-2026-89451"},"packages":[],"prev":{"headline":"iommu: Fix dev_iommu memory leak when device_add fails in iommu_mock_device_add","id":"CVE-2026-89449"},"products":["Linux"],"published":"2026-09-11","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":"A guest VM can bypass IOMMU isolation by providing an oversized virtual Stream ID that aliases to a different device, potentially enabling privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-89450/"}