Double-Free Vulnerability in regmap Package

Kernel Updated 02 Oct 2025

Summary

14/11/2021
N/A
No i
Unrated
Not published

GSD-2021-1002136: regmap: Fix possible double-free in regcache_rbtree_exit(). Affects Kernel versions >= 3f4ff561bc88b074d5e868dde4012d89cbb06c87, < 50cc1462a668dc62949a1127388bc3af785ce047. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The regmap package is a component of the Linux Kernel ecosystem. It provides a framework for accessing and manipulating hardware registers in a device-independent manner. The package is responsible for managing register caches and facilitating communication between the kernel and hardware devices. It is widely used in various Linux-based systems and plays a crucial role in device driver development and hardware interaction.

Vulnerability Detail

The identified vulnerability, with ID GSD-2021-1002136, is a possible double-free issue in the regcache_rbtree_exit() function of the regmap package. A double-free vulnerability occurs when a program attempts to free the same memory location more than once, leading to memory corruption and potential exploitation by attackers. The impact and attack plausibility of this vulnerability have not been proven yet, but it poses a potential security risk. The vulnerability was introduced in version v3.12 of the Linux Kernel and has been fixed in version v5.14.16 by commit 50cc1462a668dc62949a1127388bc3af785ce047.

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

No specific workaround has been provided for this vulnerability. It is recommended to follow the steps mentioned in the 'how_to_fix' section to address the issue.

Conclusion

The double-free vulnerability in the regmap package can potentially lead to memory corruption and exploitation. It is crucial to update the Linux Kernel to version v5.14.16 or later to mitigate this vulnerability. Additionally, reviewing and updating any device drivers or software components that rely on the regmap package is recommended. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The regmap package is a component of the Linux Kernel ecosystem that provides a framework for accessing and manipulating hardware registers in a device-independent manner.

A double-free vulnerability occurs when a program attempts to free the same memory location more than once, leading to memory corruption and potential exploitation by attackers.

The impact of this vulnerability is currently unknown. While it has the potential to be exploited by attackers, the actual impact and attack plausibility have not been proven.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.14.16 or later. Detailed steps are provided in the 'how_to_fix' section.

No specific workaround has been provided for this vulnerability. It is recommended to follow the steps mentioned in the 'how_to_fix' section to address the issue.

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