In the Linux kernel, the following vulnerability has been resolved:
dm mirror log: round up region bitmap size to BITS_PER_LONG
The code in dm-log rounds up bitset_size to 32 bits. It then uses
find_next_zero_bit_le on the allocated region. find_next_zero_bit_le
accesses the bitmap using unsigned long pointers. So, on 64-bit
architectures, it may access 4 bytes beyond the allocated size.
Fix this bug by rounding up bitset_size to BITS_PER_LONG.
This bug was found by running the lvm2 testsuite with kasan.
Metrics
Affected Vendors & Products
References
History
Thu, 17 Apr 2025 05:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-125 | |
Metrics |
cvssV3_1
|
cvssV3_1
|
Thu, 27 Feb 2025 01:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Wed, 26 Feb 2025 02:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | In the Linux kernel, the following vulnerability has been resolved: dm mirror log: round up region bitmap size to BITS_PER_LONG The code in dm-log rounds up bitset_size to 32 bits. It then uses find_next_zero_bit_le on the allocated region. find_next_zero_bit_le accesses the bitmap using unsigned long pointers. So, on 64-bit architectures, it may access 4 bytes beyond the allocated size. Fix this bug by rounding up bitset_size to BITS_PER_LONG. This bug was found by running the lvm2 testsuite with kasan. | |
Title | dm mirror log: round up region bitmap size to BITS_PER_LONG | |
References |
|
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-02-26T02:24:27.532Z
Updated: 2025-05-04T08:43:50.278Z
Reserved: 2025-02-26T02:21:30.444Z
Link: CVE-2022-49710

No data.

Status : Received
Published: 2025-02-26T07:01:46.800
Modified: 2025-02-26T07:01:46.800
Link: CVE-2022-49710
