CVE-2026-99568: Linux kernel · iommufd/iova_bitmap: Ensure that iova_bitmap_set() handles the full IOVA
Source GCVE Database
Not known to be exploited · fixed in f41d317be00767e81ce0a664fa37ab829654ab8d : update Linux kernel when convenient.
Data as of 20 Nov 2026, 07:34 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f41d317be00767e81ce0a664fa37ab829654ab8d, e21952d72b4740f08a272d694cca223b6b0099ca, dd2f8565e68cac312451926ce2e3883923caf081 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Linux kernel to f41d317be00767e81ce0a664fa37ab829654ab8d, e21952d72b4740f08a272d694cca223b6b0099ca, dd2f8565e68cac312451926ce2e3883923caf081 or 63ff69e265bec1712d2b7105e7c1556f73a3080f.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: iommufd/iova_bitmap: Ensure that iova_bitmap_set() 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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99568 (opens in a new tab)
- git.kernel.org/stable/c/63ff69e265bec1712d2b7105e7c1556f73a3080f (opens in a new tab)
- git.kernel.org/stable/c/dd2f8565e68cac312451926ce2e3883923caf081 (opens in a new tab)
- git.kernel.org/stable/c/e21952d72b4740f08a272d694cca223b6b0099ca (opens in a new tab)
- git.kernel.org/stable/c/f41d317be00767e81ce0a664fa37ab829654ab8d (opens in a new tab)