Constant-Time Key Printing Vulnerability in dm crypt

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1002851: dm crypt: make printing of the key constant-time. Affects Kernel versions < eb27bd452e9f656cb7b1a6c091c2a84d520d6258. 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 crypt package is a component of the Linux Kernel that provides disk encryption functionality. It allows users to create encrypted block devices on top of other block devices, ensuring data confidentiality and integrity. The package utilizes cryptographic algorithms to encrypt and decrypt data on-the-fly. However, a vulnerability has been discovered in the package that affects the printing of encryption keys.

Vulnerability Detail

The vulnerability in dm crypt involves the printing of encryption keys in a non-constant-time manner. This means that the time taken to print the key may vary depending on the key's value, allowing an attacker to potentially infer information about the key through timing analysis. By exploiting this vulnerability, an attacker could gain unauthorized access to encrypted data or compromise the security of the encryption mechanism.

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 →

Conclusion

The constant-time key printing vulnerability in dm crypt can be mitigated by updating the Linux Kernel to version v5.18.2 or later. This update ensures that the printing of encryption keys is performed in a constant-time manner, eliminating the timing side-channel vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

dm crypt is a component of the Linux Kernel that provides disk encryption functionality. It allows users to create encrypted block devices on top of other block devices, ensuring data confidentiality and integrity.

The vulnerability in dm crypt could allow an attacker to infer information about encryption keys through timing analysis. This could lead to unauthorized access to encrypted data or compromise the security of the encryption mechanism.

To fix this vulnerability, update your Linux Kernel to version v5.18.2 or later, which includes the fix for the constant-time key printing issue in dm crypt.

No specific workarounds have been provided for this vulnerability. It is recommended to update the Linux Kernel to the latest version to address the issue.

For more information about this vulnerability, you can refer to the source link provided in the database specific section of the vulnerability details.

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