# CVE-2026-98002: linux: In the Linux kernel, the following vulnerability has been resolved:  iommu/amd: Fix ineffective error check in nested...

CVE-2026-98002 is fixed in linux on 1 platform by DEBIAN-CVE-2026-98002 (version 7.2.7-1), released October 2, 2026. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2026-98002
- Priority: High
- CVSS: 7.8 (high)
- EPSS: 0.0011
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Sep 25, 2026

## Description

In the Linux kernel, the following vulnerability has been resolved:  iommu/amd: Fix ineffective error check in nested domain allocation  amd_iommu_pdom_id_alloc() returns an int: a domain ID on success, or the negative errno from ida_alloc_range() when the ID space is exhausted or memory is short.  amd_iommu_alloc_domain_nested() stores that return value in gdom_info->hdom_id, which is a u32, and only then tests it:  	gdom_info->hdom_id = amd_iommu_pdom_id_alloc(); 	if (gdom_info->hdom_id <= 0) {  The assignment discards the sign, so -ENOSPC becomes 0xffffffe4 and the test never fires.  The nested domain is then set up with a host domain ID that was never allocated, instead of the allocation failing with -ENOSPC.  Keep the value in an int, test it there, and store it only once it is known to be valid, which is what the other amd_iommu_pdom_id_alloc() callers already do.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 14 | 7.2.7-1 | [DEBIAN-CVE-2026-98002](https://patchblox.com/security/data/fix/linux/debian-cve-2026-98002.md) | Oct 2, 2026 |

---

Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.