Linux Kernel up to 7.2-rc2 dm-log out-of-bounds write

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$5k-$25k0.47

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.2-rc2. It has been rated as very critical. Affected by this issue is some unknown functionality of the component dm-log. This manipulation causes out-of-bounds write. This vulnerability appears as CVE-2026-72105. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 7.2-rc2 and classified as very critical. Affected by this vulnerability is an unknown function of the component dm-log. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. The CWE definition for the vulnerability is CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2026-72105 since 08/09/2026. The exploitation appears to be easy. The attack can be launched remotely. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/15/2026).

Upgrading to version 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5 or 7.2-rc3 eliminates this vulnerability. Applying the patch cdc4ddf9db2cb79f4ab86b1a509b7ac21b0b6cf5/4b0de5a3ac1fd42acb0dc1f80ac5747e3287d723/567602fa72d57169365cbc589e0b8c3be900636d/d05e0edfecf5260e6dddd28b2f0cce02bfc6ed7a/1c3412b584e1fb6c665ff33ba7259253bc0082cb/e0b0163a65758ec3a2361ae1cea407898c27f21e/79feb87ab2396d49b9b65e4bb815d33cc71cba47/9743132a41f4d9d0e54c5f2adcb821b04796bab1 is able to eliminate this problem.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.9
VulDB Meta Temp Score: 9.5

VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Out-of-bounds write
CWE: CWE-787 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.261/5.15.212/6.1.178/6.6.145/6.12.97/6.18.40/7.1.5/7.2-rc3
Patch: cdc4ddf9db2cb79f4ab86b1a509b7ac21b0b6cf5/4b0de5a3ac1fd42acb0dc1f80ac5747e3287d723/567602fa72d57169365cbc589e0b8c3be900636d/d05e0edfecf5260e6dddd28b2f0cce02bfc6ed7a/1c3412b584e1fb6c665ff33ba7259253bc0082cb/e0b0163a65758ec3a2361ae1cea407898c27f21e/79feb87ab2396d49b9b65e4bb815d33cc71cba47/9743132a41f4d9d0e54c5f2adcb821b04796bab1

Timelineinfo

08/09/2026 CVE reserved
08/15/2026 +6 days Advisory disclosed
08/15/2026 +0 days VulDB entry created
08/15/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-72105 (🔒)
GCVE (CVE): GCVE-0-2026-72105
GCVE (VulDB): GCVE-100-390523

Entryinfo

Created: 08/15/2026 12:17
Changes: 08/15/2026 12:17 (58)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!