CVE-2026-68145
CVE CVE-2026-68145EUVD EUVD-2026-55529Published 2026-08-10T11:59:09.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: iomap: fix out-of-bounds bitmap_set() with zero-length range ifs_set_range_dirty() and ifs_set_range_uptodate() compute last_blk as (off + len - 1) >> i_blkbits. When off is 0 and len is 0, the unsigned subtraction underflows to SIZE_MAX, producing a huge last_blk and nr_blks value that causes bitmap_set() to write far beyond the ifs->state allocation. Regarding ifs_set_range_uptodate(), it is temporarily safe because len cannot be passed in as 0. However, for ifs_set_range_dirty() this is reachable from __iomap_write_end(): when copy_folio_from_iter_atomic() returns 0 (e.g. user buffer fault) and the folio is already uptodate, the guard at the top of __iomap_write_end() does not trigger because !folio_test_uptodate() is false, and iomap_set_range_dirty() is called with copied == 0. Add a !len guard to both functions before the computation, so that a zero-length range is a no-op.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 4ce02c67972211be488408c275c8fbf19faf29b3 <7037e7bdcd26f46c080b8ce307dee5cb471c4b7c; patch: 6.12.101; 4ce02c67972211be488408c275c8fbf19faf29b3 <fb4fad9105c88b1d82f1b3c39e3b6abea8249af6; patch: 7.2-rc5; patch: 0; 4ce02c67972211be488408c275c8fbf19faf29b3 <9c7d8f7c8994c790fca501dc45ce66e7356cbe05; 4ce02c67972211be488408c275c8fbf19faf29b3 <c5b6a48a8a716a7730e39af1cad083dc4ec955ce; patch: 6.18.42; 6.6; patch: 7.1.6
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.