Null Pointer Dereference in pinctrl: renesas: rzn1

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002721: pinctrl: renesas: rzn1: Fix possible null-ptr-deref in sh_pfc_map_resources(). Affects Kernel versions < 01f9e02e0f13df3fd291676dc80054e977be1601. 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 pinctrl: renesas: rzn1 package is a component of the Linux Kernel that provides pin control functionality for Renesas RZ/N1 SoCs. It allows for the configuration and management of pin multiplexing, input/output settings, and other related features. This vulnerability affects the package and can lead to a null pointer dereference in the sh_pfc_map_resources() function.

Vulnerability Detail

The vulnerability arises due to a possible null pointer dereference in the sh_pfc_map_resources() function of the pinctrl: renesas: rzn1 package. This can occur when certain resources are being mapped, potentially leading to a crash or other unexpected behavior. 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 the Linux Kernel version v5.18.3 by commit 01f9e02e0f13df3fd291676dc80054e977be1601.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.18.3 or later. This can be done by pulling the latest changes from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) or by applying the specific commit 01f9e02e0f13df3fd291676dc80054e977be1601.

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 mentioned for this vulnerability.

Conclusion

The pinctrl: renesas: rzn1 package in the Linux Kernel is vulnerable to a null pointer dereference issue in the sh_pfc_map_resources() function. It is recommended to update the kernel to version v5.18.3 or later to fix this vulnerability. If you need further assistance or support in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability is not yet proven, but it could potentially lead to crashes or other unexpected behavior.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and it will provide real-time alerts for open-source vulnerabilities.

Yes, the vulnerability has been fixed in the Linux Kernel version v5.18.3 by commit 01f9e02e0f13df3fd291676dc80054e977be1601.

There is no specific workaround mentioned for this vulnerability. It is recommended to update the kernel as soon as possible.

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 Linux Kernel to version v5.18.3 or later. This can be done by pulling the latest changes from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) or by applying the specific commit 01f9e02e0f13df3fd291676dc80054e977be1601.

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.