Skip to main content

Linux Kernel CVE-2026-72105

| EUVDEUVD-2026-59063 HIGH
2026-08-15 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-gg95-xc64-46gm
7.8
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.0 HIGH

AC:H reflects dual constraints: 32-bit architecture required and region_size must be near UINT_MAX - both are uncommon conditions.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
4.0 MEDIUM
AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 17, 2026 - 06:51 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
7.8 (HIGH)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 06:21 cve.org
HIGH 7.8
CVE Published
Aug 15, 2026 - 06:21 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

AnalysisAI

Integer wraparound in the Linux kernel's dm-log subsystem on 32-bit architectures allows a local attacker to trigger a bitset_size overflow, potentially causing kernel memory corruption. Specifically, when region_size is close to UINT_MAX and bitset_size is rounded up to a multiple of BITS_PER_LONG, a 32-bit size_t wraps around to zero, leading to an incorrect zero-byte bitmap allocation and subsequent out-of-bounds write conditions. No public exploit is identified at time of analysis, and EPSS probability is low (0.22%, percentile 13%), but the CVSS 7.8 local score reflects the potential for full system compromise once the specific conditions are met.

Technical ContextAI

The Device Mapper log (dm-log) subsystem in the Linux kernel tracks dirty regions for mirrored block devices, typically in RAID1 configurations. The vulnerability resides in the bitset_size calculation: when region_count is valid but close to UINT_MAX, rounding it up to the nearest multiple of BITS_PER_LONG produces a value of 2^32, which overflows a 32-bit size_t to zero. The subsequent division by 8 to convert bits to bytes then yields a zero-length allocation for the dirty-region bitmap. A prior fix (commit c20e36b7631d, tagged CWE for region_count overflow) addressed the region_count field but left the derived bitset_size calculation unguarded. The fix requires special-casing a zero result after rounding to detect rollover and set bitset_size to the correct byte count for 2^32 bits. The flaw is architecturally constrained: on 64-bit systems, size_t is 64 bits and the overflow cannot occur. No CWE identifier has been officially assigned, but this is a classic integer overflow/wraparound leading to a buffer overflow, consistent with CWE-190 and CWE-787.

RemediationAI

The primary remediation is upgrading the Linux kernel to a patched stable release: 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5, or any 7.2+ release, as appropriate for the running branch. Patches are available via the kernel stable tree at https://git.kernel.org/stable. Distribution vendors (Debian, Ubuntu, RHEL, etc.) are expected to backport these fixes; consult distribution security advisories for package-level updates. For systems that cannot be patched immediately and are running 32-bit kernels with dm-log in use, the most effective compensating control is to avoid configuring dm-log with region sizes that approach UINT_MAX - this is a non-default, unusual configuration, so simply auditing existing device mapper setups for extreme region parameters substantially reduces exposure. Migrating from 32-bit to 64-bit kernel builds eliminates the vulnerability entirely, as size_t overflow cannot occur on 64-bit. There is no known risk to 64-bit deployments and no action is needed there.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-72105 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy