{"api_version":"1","generated_at":"2026-09-25T22:31:28+00:00","cve":"CVE-2026-98002","urls":{"html":"https://cve.report/CVE-2026-98002","api":"https://cve.report/api/cve/CVE-2026-98002.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98002","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98002"},"summary":{"title":"iommu/amd: Fix ineffective error check in nested domain allocation","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->hdom_id, which is a u32, and only then tests it:\n\n\tgdom_info->hdom_id = amd_iommu_pdom_id_alloc();\n\tif (gdom_info->hdom_id <= 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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-25 11:17:28","updated_at":"2026-09-25 15:18:03"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"HIGH","privilegesRequired":"LOW","userInteraction":"NONE","scope":"CHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","data":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/fa5c0827f0b7bac6d0a188f10118151769ae68fd","name":"https://git.kernel.org/stable/c/fa5c0827f0b7bac6d0a188f10118151769ae68fd","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/80c231f5577229d1e90a1e312b3095f9502f8625","name":"https://git.kernel.org/stable/c/80c231f5577229d1e90a1e312b3095f9502f8625","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98002","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98002","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 757d2b1fdf5b7d6eead5963a49b5780617987ab8 80c231f5577229d1e90a1e312b3095f9502f8625 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 757d2b1fdf5b7d6eead5963a49b5780617987ab8 fa5c0827f0b7bac6d0a188f10118151769ae68fd git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.0","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.7 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/iommu/amd/nested.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"80c231f5577229d1e90a1e312b3095f9502f8625","status":"affected","version":"757d2b1fdf5b7d6eead5963a49b5780617987ab8","versionType":"git"},{"lessThan":"fa5c0827f0b7bac6d0a188f10118151769ae68fd","status":"affected","version":"757d2b1fdf5b7d6eead5963a49b5780617987ab8","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/iommu/amd/nested.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"7.0"},{"lessThan":"7.0","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.7","versionStartIncluding":"7.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc3","versionStartIncluding":"7.0","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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->hdom_id, which is a u32, and only then tests it:\n\n\tgdom_info->hdom_id = amd_iommu_pdom_id_alloc();\n\tif (gdom_info->hdom_id <= 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."}],"metrics":[{"cvssV3_1":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:L - The patched function amd_iommu_alloc_domain_nested() is reached only via the IOMMU_HWPT_ALLOC ioctl on a local iommufd fd (/dev/iommu) against an AMD vIOMMU (iommufd_hwpt_alloc -> viommu->ops->alloc_domain_nested); no remote protocol carries the input.\nAC:H - The failure path needs ida_alloc_range() in amd_iommu_pdom_id_alloc() to fail: either all 65535 global host domain IDs are in use with a victim domain holding 0xffe4, which lowest-first allocation doesn't let the attacker arrange on demand, or a GFP_ATOMIC failure the attacker cannot force.\nPR:L - Needs a VMM-style user that has been given /dev/iommu (0660) and a bound VFIO device cdev to create a vIOMMU and nested HWPTs; that is delegated device access, not full init-namespace root.\nUI:N - The attacker allocates the nested HWPTs and attaches the device themselves; nobody else has to do anything.\nS:C - The unallocated hdom_id (truncated to 0xffe4/0xfff4 by DTE_DOMID_MASK) is written into the DTE by set_dte_nested(), so the nested device shares IOTLB tags with another IOMMU domain, breaking the DMA isolation boundary between domains.\nC:H - Because the DomID is aliased, the device's DMA can hit IOTLB translations cached for the other domain and read memory belonging to that domain.\nI:H - The same aliased IOTLB entries let the device's DMA writes land in the other domain's pages, corrupting memory outside the nested domain.\nA:H - Stray DMA writes into another domain's memory, plus invalidations for the parent S2 hitting the shared hdom_id, can corrupt host or guest memory used by other devices and bring them down."}]}],"providerMetadata":{"dateUpdated":"2026-09-25T14:41:49.625Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/80c231f5577229d1e90a1e312b3095f9502f8625"},{"url":"https://git.kernel.org/stable/c/fa5c0827f0b7bac6d0a188f10118151769ae68fd"}],"title":"iommu/amd: Fix ineffective error check in nested domain allocation","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98002","datePublished":"2026-09-25T10:23:29.929Z","dateReserved":"2026-09-25T10:19:56.068Z","dateUpdated":"2026-09-25T14:41:49.625Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-25 11:17:28","lastModifiedDate":"2026-09-25 15:18:03","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"HIGH","privilegesRequired":"LOW","userInteraction":"NONE","scope":"CHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1.1,"impactScore":6}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98002","Ordinal":"1","Title":"iommu/amd: Fix ineffective error check in nested domain allocati","CVE":"CVE-2026-98002","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98002","Ordinal":"1","NoteData":"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->hdom_id, which is a u32, and only then tests it:\n\n\tgdom_info->hdom_id = amd_iommu_pdom_id_alloc();\n\tif (gdom_info->hdom_id <= 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.","Type":"Description","Title":"iommu/amd: Fix ineffective error check in nested domain allocati"}]}}}