CVE-2026-72105

dm-log: fix a bitset_size overflow on 32bit machines

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 05:52 AM UTC
Updated: October 19, 2026 at 10:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

12bd5b88e91a02785244ff1d20fb157e96e9cdc83ec74da927b4e171a6fc0e77b1188ba4d019af5144ab8875ae4a2842bde2d756bed195d375e0debb4ec8323b9f0764a14d532b1ae9b87f8a9fecb8675.10.2585.15.2096.1.1756.12.916.18.336.6.1417.0.107.1b455903eed4558982be0811f5b7f44f6bbc4ff57c20e36b7631d83e7535877f08af8b0af72c44b1ad4ac87567f86a55c3c92e9a5144dcd943a9772a1defe483e47173768c227532694dc78cb65db5f09
Vendor states this is fixed in 1c3412b584e1fb6c665ff33ba7259253bc0082cb (fixed)
Vendor states this is fixed in 4b0de5a3ac1fd42acb0dc1f80ac5747e3287d723 (fixed)
Vendor states this is fixed in 567602fa72d57169365cbc589e0b8c3be900636d (fixed)
Vendor states this is fixed in 79feb87ab2396d49b9b65e4bb815d33cc71cba47 (fixed)
Vendor states this is fixed in 9743132a41f4d9d0e54c5f2adcb821b04796bab1 (fixed)
Vendor states this is fixed in cdc4ddf9db2cb79f4ab86b1a509b7ac21b0b6cf5 (fixed)
Vendor states this is fixed in d05e0edfecf5260e6dddd28b2f0cce02bfc6ed7a (fixed)
Vendor states this is fixed in e0b0163a65758ec3a2361ae1cea407898c27f21e (fixed)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-190

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card