Answer in brief
CVE-2026-72105 records a High severity (CVSS 7.8) vulnerability in dm-log: fix a bitset_size overflow on 32bit machines. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=44ab8875ae4a2842bde2d756bed195d375e0debb <cdc4ddf9db2cb79f4ab86b1a509b7ac21b0b6cf5 || >=defe483e47173768c227532694dc78cb65db5f09 <4b0de5a3ac1fd42acb0dc1f80ac5747e3287d723 || >=3ec74da927b4e171a6fc0e77b1188ba4d019af51 <567602fa72d57169365cbc589e0b8c3be900636d || >=d4ac87567f86a55c3c92e9a5144dcd943a9772a1 <d05e0edfecf5260e6dddd28b2f0cce02bfc6ed7a || >=12bd5b88e91a02785244ff1d20fb157e96e9cdc8 <1c3412b584e1fb6c665ff33ba7259253bc0082cb || >=b455903eed4558982be0811f5b7f44f6bbc4ff57 <e0b0163a65758ec3a2361ae1cea407898c27f21e || >=c20e36b7631d83e7535877f08af8b0af72c44b1a <79feb87ab2396d49b9b65e4bb815d33cc71cba47 || >=c20e36b7631d83e7535877f08af8b0af72c44b1a <9743132a41f4d9d0e54c5f2adcb821b04796bab1 || 4ec8323b9f0764a14d532b1ae9b87f8a9fecb867 || >=5.10.258 <5.10.261 || >=5.15.209 <5.15.212 || >=6.1.175 <6.1.178 || >=6.6.141 <6.6.145 || >=6.12.91 <6.12.97 || >=6.18.33 <6.18.40 || >=7.0.10 <7.1 | cdc4ddf9db2cb79f4ab86b1a509b7ac21b0b6cf5, 4b0de5a3ac1fd42acb0dc1f80ac5747e3287d723, 567602fa72d57169365cbc589e0b8c3be900636d, d05e0edfecf5260e6dddd28b2f0cce02bfc6ed7a, 1c3412b584e1fb6c665ff33ba7259253bc0082cb, e0b0163a65758ec3a2361ae1cea407898c27f21e, 79feb87ab2396d49b9b65e4bb815d33cc71cba47, 9743132a41f4d9d0e54c5f2adcb821b04796bab1, 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1 |
| Linux/Linuxgeneric | 7.1 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: dm-log: fix a bitset_size overflow on 32bit machines Commit c20e36b7631d ("dm log: fix out-of-bounds write due to region_count overflow") made sure that region_count could fit in an unsigned int. But the bitmap memory isn't allocated based on region_count. It uses bitset_size (a size_t variable). The first step of calculating bitset_size is to set it to region_count, rounded up to a multiple of BITS_PER_LONG. If region_size is less than BITS_PER_LONG smaller than UINT_MAX, it will get rounded up to 2^32. On a 32bit architecture, this will make bitset_size wrap around to 0 and fail, despite region_count being valid. Since bitset_size gets divided by 8, it can hold any valid region_count. It just needs a special case to handle the rollover. If it is 0, the value rolled over, and bitset size should be set to the number of bytes needed to hold 2^32 bits.
Quoted source text, attributed separately from HOL analysis.