Vulnerability in dm verity: fix require_signatures module_param permissions

Kernel Updated 02 Oct 2025

Summary

30/06/2021
N/A
No i
Unrated
Not published

GSD-2021-1001016: dm verity: fix require_signatures module_param permissions. Affects Kernel versions < fb429fad145a987056ac315b2c859197c3daa890. 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 verity package is a component of the Linux Kernel ecosystem. It provides integrity checking for block devices, ensuring that data remains unaltered. The package includes a module_param called require_signatures, which controls the requirement for signed data. However, there is a vulnerability in the permissions of this module_param, which can potentially be exploited.

Vulnerability Detail

The vulnerability in dm verity's require_signatures module_param permissions allows unauthorized users to modify the requirement for signed data. This can lead to the execution of unsigned or tampered code, compromising the integrity of the system. The impact of this vulnerability depends on the specific usage of dm verity and the potential exploitation scenarios.

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

As a workaround, users can manually modify the permissions of the require_signatures module_param to restrict access. This can be done by modifying the relevant code in the Linux Kernel source files. However, it is strongly advised to apply the official fix by updating the Kernel to the recommended version.

Conclusion

In conclusion, the vulnerability in dm verity's require_signatures module_param permissions can be mitigated by updating the Linux Kernel to version v5.12.11 or later. It is important to promptly apply the fix to ensure the proper security of the require_signatures module_param. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

dm verity is a component of the Linux Kernel that provides integrity checking for block devices, ensuring data remains unaltered.

The vulnerability allows unauthorized users to modify the requirement for signed data, potentially leading to the execution of unsigned or tampered code.

To fix this vulnerability, update the Linux Kernel to version v5.12.11 or later, which includes a commit that addresses the issue.

Yes, a workaround involves manually modifying the permissions of the require_signatures module_param in the Linux Kernel source files. However, it is recommended to apply the official fix by updating the Kernel.

For more details about this vulnerability, refer to the provided references link in the vulnerability details section.

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