CVE-2026-99568: iommufd/iova_bitmap: Ensure that iova_bitmap_set() handles the full IOVA

Published Nov 20, 2026
·
Updated

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

7 affected componentsFixes available
linux/kernel>=6.1.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:49 AM
Data Sourced
via MITRE·05:49 AM
Description
Data Sourced
via OSV·05:49 AM
DescriptionAffected Software
Data Sourced
via NVD·06:17 AM
Description

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203