Skip to main content
Menu
CVEs

Linux kernel out-of-bounds write in iommufd IOVA bitmap

CVE-2026-99568Published November 20, 2026, updated

Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The Linux kernel's iommufd IOVA bitmap code can lose dirty-page tracking when a bitmap ends in the middle of a large page table entry, and it lacks bounds checking that could let it write memory beyond what userspace expects. The fix makes the function return an error when this condition occurs.

Written by a model

Original 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.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-99568 (iommufd/iova_bitmap: Ensure that iova_bitmap_set() handles the full IOVA), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99568 (entry last updated 2026-11-20):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 6.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99568 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99568 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/f41d317be00767e81ce0a664fa37ab829654ab8d
- https://git.kernel.org/stable/c/63ff69e265bec1712d2b7105e7c1556f73a3080f
- https://git.kernel.org/stable/c/dd2f8565e68cac312451926ce2e3883923caf081
- https://git.kernel.org/stable/c/e21952d72b4740f08a272d694cca223b6b0099ca
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99568
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99568"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 47 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 6

Questions about CVE-2026-99568

Is CVE-2026-99568 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-99568?

Linux: version 6.1.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.