iommu/amd: Fix ineffective error check in nested domain allocation
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 80c231f5577229d1e90a1e312b3095f9502f8625 and Kernel fa5c0827f0b7bac6d0a188f10118151769ae68fd.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.0, >=757d2b1fdf5b7d6eead5963a49b5780617987ab8 <80c231f5577229d1e90a1e312b3095f9502f8625, >=757d2b1fdf5b7d6eead5963a49b5780617987ab8 <fa5c0827f0b7bac6d0a188f10118151769ae68fd | 80c231f5577229d1e90a1e312b3095f9502f8625, fa5c0827f0b7bac6d0a188f10118151769ae68fd |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket