Vulnerability in dm mirror log: round up region bitmap size to BITS_PER_LONG

Kernel Updated 02 Oct 2025

Summary

31/07/2022
N/A
No i
Unrated
Not published

GSD-2022-1004642: dm mirror log: round up region bitmap size to BITS_PER_LONG. Affects Kernel versions >= 29121bd0b00ebb9524971a583fea4a2f7afe8041, < ba751f0d25f07aa21ce9b85372a3792bf7969d13. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The dm mirror log is a component of the Linux Kernel that provides mirroring functionality for device mapper targets. It maintains a log of changes made to mirrored regions on disk. The region bitmap is used to track the status of each region, indicating whether it is in sync or needs to be resynchronized. This vulnerability arises from a failure to round up the region bitmap size to BITS_PER_LONG, which can lead to memory corruption and potential security issues.

Vulnerability Detail

The vulnerability occurs due to an incorrect calculation of the region bitmap size in the dm mirror log. The size is not rounded up to the nearest multiple of BITS_PER_LONG, which can result in memory corruption and potential security vulnerabilities. An attacker may be able to exploit this vulnerability to gain unauthorized access, modify data, or cause a denial of service. The impact and attack plausibility of this vulnerability have not been proven yet.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel.

Conclusion

In conclusion, the dm mirror log vulnerability in the Linux Kernel arises from an incorrect calculation of the region bitmap size. This can lead to memory corruption and potential security issues. It is recommended to update the Linux Kernel to the latest version to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The dm mirror log is a component of the Linux Kernel that provides mirroring functionality for device mapper targets. It maintains a log of changes made to mirrored regions on disk.

BITS_PER_LONG is a constant defined in the Linux Kernel that represents the number of bits in a long integer. It is architecture-dependent and typically set to 32 or 64 bits.

This vulnerability can lead to memory corruption and potential security issues. An attacker may be able to exploit it to gain unauthorized access, modify data, or cause a denial of service.

No, the impact and attack plausibility of this vulnerability have not been proven yet. However, it is still recommended to apply the fix as a precautionary measure.

To update the Linux Kernel, you can follow the instructions provided by your Linux distribution or refer to the official documentation for the specific steps.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback