CVE-2026-99568: iommufd/iova_bitmap: Ensure that iova_bitmap_set() handles the full IOVA
In the Linux kernel, the following vulnerability has been resolved:
iommufd/iovabitmap: Ensure that iovabitmapset() handles the full IOVA
Generally userspace is going to step the dirty bitmap through the IOVA space. However if the bitmap ends in the middle of a large PTE this is problematic. The first step will clear the dirty bit and report dirty to the end of its bitmap while the second step will see the clear'd dirty and report clean for the start of the bitmap. If it happens this ends up losing dirties.
Further this function is missing bounds checking so if this does happen ther is a good chance it will write memory beyond what the userspace was expecting.
Return an error code if this illegal condition happens.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1
Event History
Frequently Asked Questions
Who is exposed to this issue?
Systems using the Linux kernel iommufd dirty-bitmap functionality are exposed when userspace iterates a dirty bitmap across IOVA space and the bitmap range ends in the middle of a large PTE.
What condition triggers the vulnerability?
The problematic condition occurs when a userspace bitmap request ends partway through a large PTE. A first bitmap step can clear and report the dirty state through its endpoint, while a later step reports the beginning as clean, causing dirty information to be lost.
What is the potential impact?
Dirty IOVA state can be lost, and the missing bounds checking creates a likelihood that iova_bitmap_set() writes beyond the memory range userspace expected.
What happens after the fix is applied?
The corrected behavior returns an error when this illegal bitmap boundary condition occurs, rather than processing the partial large-PTE range.