{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98002 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98002 is a high-severity vulnerability in Linux, published on 25 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-98002 and fix it if it is affected.\n\nWhat it is: CVE-2026-98002 is a high-severity vulnerability in Linux, published on 25 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-98002 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-98002/ (Markdown: https://insights.sbomify.com/CVE-2026-98002/index.md)","id":"CVE-2026-98002","markdown":"https://insights.sbomify.com/CVE-2026-98002/index.md","name":"CVE-2026-98002","record":{"aliases":["DEBIAN-CVE-2026-98002","GHSA-38jm-2gpc-m9wh","UBUNTU-CVE-2026-98002"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel IOMMU","requires_auth":"low_privilege","summary":"An integer overflow in AMD IOMMU nested domain allocation causes error checks to fail, potentially leading to undefined behavior or resource exhaustion.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/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/amd: Fix ineffective error check in nested domain allocation\n\namd_iommu_pdom_id_alloc() returns an int: a domain ID on success, or the\nnegative errno from ida_alloc_range() when the ID space is exhausted or\nmemory is short.  amd_iommu_alloc_domain_nested() stores that return value\nin gdom_info-\u003ehdom_id, which is a u32, and only then tests it:\n\n\tgdom_info-\u003ehdom_id = amd_iommu_pdom_id_alloc();\n\tif (gdom_info-\u003ehdom_id \u003c= 0) {\n\nThe assignment discards the sign, so -ENOSPC becomes 0xffffffe4 and the\ntest never fires.  The nested domain is then set up with a host domain ID\nthat was never allocated, instead of the allocation failing with -ENOSPC.\n\nKeep the value in an int, test it there, and store it only once it is\nknown to be valid, which is what the other amd_iommu_pdom_id_alloc()\ncallers already do.","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/amd: Fix ineffective error check in nested domain allocation","id":"CVE-2026-98002","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"iommu/amd: Do not reallocate GA log buffers on resume","id":"CVE-2026-98003"},"packages":[],"prev":{"headline":"hwmon: (ltc4282) Make sure clk_init_data is fully initialized","id":"CVE-2026-98001"},"products":["Linux"],"published":"2026-09-25","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":"An integer overflow in AMD IOMMU nested domain allocation causes error checks to fail, potentially leading to undefined behavior or resource exhaustion.","url":"https://insights.sbomify.com/CVE-2026-98002/"}