Vulnerability in Kernel package: clk-rcg2

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1001813: clk: qcom: clk-rcg2: Update logic to calculate D value for RCG. Affects Kernel versions >= 99cbd064b059f222c8839ba433a68b2d6ee33066, < 34dca60982e93e69ae442aa2d36ce61c9a3bb563. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Kernel package is a critical component of the Linux operating system, responsible for managing various system resources and providing essential functionalities. One of its modules, clk-rcg2, is used for calculating the D value for RCG (Rate Change Gear) in Qualcomm processors. This functionality is crucial for maintaining the clock frequency and performance of the processor. However, a vulnerability has been discovered in the logic used to calculate the D value, which could potentially lead to security issues.

Vulnerability Detail

The vulnerability in clk-rcg2 arises from a flaw in the logic used to calculate the D value for RCG in Qualcomm processors. An attacker could potentially exploit this vulnerability to manipulate the clock frequency of the processor, leading to various security risks. The impact and attack plausibility of this vulnerability have not been proven yet. It is important to note that this vulnerability has been fixed in Linux Kernel version v5.15.33 by commit 34dca60982e93e69ae442aa2d36ce61c9a3bb563. However, it was introduced in version v3.16 by commit 99cbd064b059f222c8839ba433a68b2d6ee33066.

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

If updating the Kernel package is not immediately feasible, a temporary workaround can be implemented. It involves modifying the affected code in clk-rcg2 to address the vulnerability. Here is an example of the code modification:

// Original code
int d_value = calculate_d_value();

// Workaround code
int d_value = calculate_d_value_fixed();

Conclusion

The vulnerability in the Kernel package's clk-rcg2 module could potentially lead to security risks by allowing attackers to manipulate the clock frequency of Qualcomm processors. It is crucial to update the Kernel package to version v5.15.33 or later to fix this vulnerability. Alternatively, a temporary workaround can be implemented by modifying the affected code. Regularly checking for vulnerabilities using tools like Vulert can help ensure the security of your system. For further support and assistance, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability can vary depending on the attacker's intentions and the system's configuration. However, potential consequences include unauthorized access, privilege escalation, and denial of service attacks.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will analyze it for any known vulnerabilities.

As of now, there are no known exploits for this vulnerability. However, it is crucial to apply the fix or workaround as soon as possible to mitigate any potential risks.

Yes, this vulnerability can be exploited remotely if the attacker can gain access to the targeted system. It is important to ensure that the Kernel package is updated or the workaround is implemented to prevent any remote exploitation.

For further support and assistance in vulnerability remediation, you can reach out to info@devnack.com. Our team of experts will be happy to assist you.

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