iommu/io-pgtable-arm: fix size_t signedness bug in unmap path
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 41ec6988547819756fb65e94fc24f3e0dddf84ac, Kernel 6.18.8 and Kernel 374e7af67d9d9d6103c2cfc8eb32abfecf3a2fd8.
In the Linux kernel, the following vulnerability has been resolved: iommu/io-pgtable-arm: fix size_t signedness bug in unmap path __arm_lpae_unmap() returns size_t but was returning -ENOENT (negative error code) when encountering an unmapped PTE. Since size_t is unsigned, -ENOENT (typically -2) becomes a huge positive value (0xFFFFFFFFFFFFFFFE on 64-bit systems). This corrupted value propagates through the call chain: __arm_lpae_unmap() returns -ENOENT as size_t -> arm_lpae_unmap_pages() returns it -> __iommu_unmap() adds it to iova address -> iommu_pgsize() triggers BUG_ON due to corrupted iova This can cause IOVA address overflow in __iommu_unmap() loop and trigger BUG_ON in iommu_pgsize() from invalid address alignment. Fix by returning 0 instead of -ENOENT. The WARN_ON already signals the error condition, and returning 0 (meaning "nothing unmapped") is the correct semantic for size_t return type. This matches the behavior of other io-pgtable implementations (io-pgtable-arm-v7s, io-pgtable-dart) which return 0 on error conditions.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=3318f7b5cefbff96b1bb49584ac38d2c9997a830 <41ec6988547819756fb65e94fc24f3e0dddf84ac, =6.19, >=6.16 <6.18.8, =6.16, >=3318f7b5cefbff96b1bb49584ac38d2c9997a830 <374e7af67d9d9d6103c2cfc8eb32abfecf3a2fd8 | 41ec6988547819756fb65e94fc24f3e0dddf84ac, 6.18.8, 374e7af67d9d9d6103c2cfc8eb32abfecf3a2fd8 |
| linux-kernel: Kernel | >=6.16.0 <6.18.8 | 6.18.8 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket