Memory Leak in Renesas-rpc-if in Linux Kernel

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1000966: memory: renesas-rpc-if: fix platform-device leak in error path. Affects Kernel versions >= ca7d8b980b67f133317525c4273e144116ee1ae5, < 66b9b707ea4dcafca92b6261c6924652914e3b73. 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 Renesas-rpc-if is a memory management component in the Linux Kernel. It provides an interface for communication between the Renesas RPC (Remote Procedure Call) protocol and the platform devices. The RPC protocol is commonly used in embedded systems for inter-process communication. The vulnerability in the Renesas-rpc-if component leads to a memory leak in the error path, which can result in resource exhaustion and potential system instability.

Vulnerability Detail

The vulnerability in the Renesas-rpc-if component of the Linux Kernel allows for a memory leak in the error path. When an error occurs during the execution of the RPC protocol, the component fails to properly release allocated resources, leading to a memory leak. This can result in the depletion of available memory, potentially causing system instability and denial of service. The vulnerability was introduced in version v5.9 of the Linux Kernel and has been fixed in version v5.17.4.

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

There is no specific workaround provided for this vulnerability. The recommended solution is to update the Linux Kernel to the fixed version.

Conclusion

The memory leak vulnerability in the Renesas-rpc-if component of the Linux Kernel can lead to resource exhaustion and system instability. It is recommended to update the Linux Kernel to version v5.17.4 or later to fix this vulnerability. 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 a memory leak, potentially causing resource exhaustion and system instability.

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 the Vulert Playground will analyze it for any known vulnerabilities.

At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.

The vulnerability itself does not provide remote code execution capabilities. However, if an attacker can trigger the error path in the Renesas-rpc-if component, they may be able to cause a memory leak remotely, potentially leading to denial of service.

The recommended solution is to update the Linux Kernel to the fixed version. However, if updating is not feasible, you can consider implementing custom patches or workarounds specific to your system. It is important to thoroughly test any custom solutions to ensure they do not introduce additional vulnerabilities.

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