GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel iomap: zero-length write range underflows into an out-of-bounds bitmap_set()

CVE-2026-68145Kernel, userspace & hypervisorcurated

Impact

iomap is the buffered-write path behind XFS and other modern filesystems, so this is core host kernel code on essentially every GPU node. When __iomap_write_end() is reached with copied == 0 (a faulting user buffer against an already-uptodate folio), the off + len - 1 subtraction underflows to SIZE_MAX and bitmap_set() writes far past the ifs->state allocation - kernel heap corruption driven by an unprivileged local process. Kernel heap corruption is not contained by the container boundary, so one tenant's job can crash or corrupt the host that every GPU on the box is attached to. The record shows the fix only; it does not demonstrate a working privilege escalation.

Who can reach it

Local and unprivileged. Any process that can write to an iomap-backed filesystem and arrange a faulting user buffer, which includes any tenant holding a container or pod on the node. No special device access and no authentication beyond having code execution on the host kernel.

What to do

Move to a stable kernel carrying the !len guard in ifs_set_range_dirty() and ifs_set_range_uptodate() (fixed across five stable branches, see the git.kernel.org commits) and reboot the node. There is no runtime mitigation - the path is the ordinary buffered write path and cannot be disabled. Budget a drain and reboot per node; the change is a two-line guard, so a livepatch may be feasible if your kernel vendor ships one.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.