https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 08:58:42 +0000 https://vulnerability.circl.lu/vuln/cve-2026-23067 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu/io-pgtable-arm: fix size_t signedness bug in unmap path</p> <p>__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).</p> <p>This corrupted value propagates through the call chain: __arm_lpae_unmap() returns -ENOENT as size_t -&gt; arm_lpae_unmap_pages() returns it -&gt; __iommu_unmap() adds it to iova address -&gt; iommu_pgsize() triggers BUG_ON due to corrupted iova</p> <p>This can cause IOVA address overflow in __iommu_unmap() loop and trigger BUG_ON in iommu_pgsize() from invalid address alignment.</p> <p>Fix by returning 0 instead of -ENOENT. The WARN_ON already signals the error condition, and returning 0 (meaning &#34;nothing unmapped&#34;) 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.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu/io-pgtable-arm: fix size_t signedness bug in unmap path</p> <p>__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).</p> <p>This corrupted value propagates through the call chain: __arm_lpae_unmap() returns -ENOENT as size_t -&gt; arm_lpae_unmap_pages() returns it -&gt; __iommu_unmap() adds it to iova address -&gt; iommu_pgsize() triggers BUG_ON due to corrupted iova</p> <p>This can cause IOVA address overflow in __iommu_unmap() loop and trigger BUG_ON in iommu_pgsize() from invalid address alignment.</p> <p>Fix by returning 0 instead of -ENOENT. The WARN_ON already signals the error condition, and returning 0 (meaning &#34;nothing unmapped&#34;) 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.</p> https://vulnerability.circl.lu/vuln/cve-2026-23067