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-1001650: memory: renesas-rpc-if: fix platform-device leak in error path. Affects Kernel versions >= ca7d8b980b67f133317525c4273e144116ee1ae5, < 05d1824a7fb43ab9adb1eb82404954af81d8c984. 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 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 renesas-rpc-if component is responsible for managing the memory resources used by the RPC protocol. However, a vulnerability has been discovered in this component that can lead to a memory leak in certain error scenarios.

Vulnerability Detail

The vulnerability in renesas-rpc-if occurs when an error condition is encountered during the initialization or setup of the RPC protocol. In such cases, the component fails to properly release the platform device, resulting in a memory leak. This can lead to a gradual depletion of available memory resources, potentially causing system instability or denial of service. The vulnerability was introduced in version v5.9 of the Linux Kernel and has been fixed in version v5.15.35.

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 available for this vulnerability. However, users can mitigate the risk by ensuring that their systems have sufficient memory resources and monitoring for any signs of memory depletion or system instability.

Conclusion

The memory leak vulnerability in renesas-rpc-if can be mitigated by updating the Linux Kernel to the latest version. It is important to ensure that systems have sufficient memory resources and monitor for any signs of memory depletion or system instability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

renesas-rpc-if is a memory management component in the Linux Kernel that provides an interface for communication between the Renesas RPC protocol and platform devices.

The vulnerability can lead to a memory leak, gradually depleting available memory resources and potentially causing system instability or denial of service.

To fix the vulnerability, update the Linux Kernel to version v5.15.35 or later.

There is no specific workaround available, but users can mitigate the risk by ensuring sufficient memory resources and monitoring for signs of memory depletion or system instability.

The vulnerability was introduced in version v5.9 of the Linux Kernel and fixed in version v5.15.35.

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