Refcount Leak in rockchip_grf_init in Kernel

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1003969: soc: rockchip: Fix refcount leak in rockchip_grf_init. Affects Kernel versions >= 4c58063d4258f6beb4fd5647db6b58f49e337c8f, < d5422f323858cad3ac3581075f9a3a5e0d41c0d8. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Kernel is a crucial component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functionalities for the proper functioning of the system. The rockchip_grf_init function is part of the Kernel's rockchip subsystem, specifically designed for Rockchip SoCs. This function initializes the General Register Files (GRFs) used for configuring various hardware settings. However, a vulnerability has been discovered in the rockchip_grf_init function that can lead to a refcount leak.

Vulnerability Detail

The refcount leak vulnerability in rockchip_grf_init arises due to improper handling of reference counts. When the function is called multiple times, it fails to release the reference count properly, resulting in a leak. This can lead to resource exhaustion and potential denial-of-service (DoS) attacks. An attacker could exploit this vulnerability to exhaust system resources, causing instability or crashes. The vulnerability was introduced in Kernel version 4.11 and fixed in version 4.14.283.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Kernel to version 4.14.283 or later. This update includes the commit d5422f323858cad3ac3581075f9a3a5e0d41c0d8, which addresses the refcount leak issue in rockchip_grf_init. Updating the Kernel ensures that the vulnerability is patched and the system is protected.

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 apply the patch manually by cherry-picking the commit d5422f323858cad3ac3581075f9a3a5e0d41c0d8 to their Kernel version. Here is an example of how to apply the patch using the git cherry-pick command:

$ git cherry-pick d5422f323858cad3ac3581075f9a3a5e0d41c0d8

By applying this patch, the refcount leak vulnerability in rockchip_grf_init can be mitigated.

Conclusion

The refcount leak vulnerability in rockchip_grf_init can have serious consequences, including resource exhaustion and potential denial-of-service attacks. It is crucial to update the Kernel to version 4.14.283 or later to ensure the vulnerability is patched. Applying the provided patch manually or using Vulert's monitoring services can help mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to resource exhaustion and potential denial-of-service (DoS) attacks. An attacker could exploit this vulnerability to exhaust system resources, causing instability or crashes.

You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just a manifest file like package-lock.json.

Yes, the vulnerability has been fixed in Kernel version 4.14.283. It is recommended to update the Kernel to this version or later to ensure the vulnerability is patched.

Yes, you can apply the patch manually by cherry-picking the commit d5422f323858cad3ac3581075f9a3a5e0d41c0d8 to your Kernel version. Instructions for applying the patch can be found in the 'how_to_fix' section of this report.

You can find more information about this vulnerability in the vulnerability database maintained by the Cloud Security Alliance. The specific vulnerability ID is GSD-2022-1003969.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Kernel to version 4.14.283 or later. This update includes the commit d5422f323858cad3ac3581075f9a3a5e0d41c0d8, which addresses the refcount leak issue in rockchip_grf_init. Updating the Kernel ensures that the vulnerability is patched and the system is protected.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.