← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-72105

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-72105

Key Details

CVECVE-2026-72105
CVSS Score / Version
7.8 (High) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-72105
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-72105
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.