Vulnerability in pinctrl: samsung package - Drop Pin Banks References on Error Paths

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1001314: pinctrl: samsung: drop pin banks references on error paths. Affects Kernel versions >= ab663789d69760d2735402f66501f20b60312a3d, < 22762140419aa06c178979aa26be59be2fee7231. 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 pinctrl: samsung package is a component of the Linux Kernel that provides pin control and GPIO functionality for Samsung SoCs. It allows the configuration and management of pin banks, which are groups of pins with similar characteristics. These pin banks are used for various purposes, including controlling input/output operations and interfacing with external devices. However, a vulnerability has been identified in the package that involves the mishandling of pin bank references on error paths.

Vulnerability Detail

The vulnerability in the pinctrl: samsung package occurs when pin banks are not properly released in certain error scenarios. This can lead to resource leaks and potential memory corruption issues. An attacker who can trigger these error paths may be able to exploit the vulnerability to gain elevated privileges, execute arbitrary code, or cause a denial-of-service condition. The vulnerability was introduced in version v3.8 of the Linux Kernel and has been fixed in version v5.17.2.

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. However, as a general security measure, it is recommended to ensure that systems running the affected package are protected by appropriate security controls, such as firewalls, intrusion detection systems, and access controls. Regularly monitoring and updating the system with the latest security patches is also crucial.

Conclusion

The vulnerability in the pinctrl: samsung package that involves the mishandling of pin bank references on error paths can lead to resource leaks and potential memory corruption. It is crucial to update the Linux Kernel to version v5.17.2 or later to mitigate the risk. Regularly monitoring for vulnerabilities using tools like Vulert can also help ensure the security of your system. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can potentially allow an attacker to gain elevated privileges, execute arbitrary code, or cause a denial-of-service condition.

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 the tool will provide real-time alerts for open-source vulnerabilities.

Yes, the vulnerability has been fixed in version v5.17.2 of the Linux Kernel. It is recommended to update to this version or later to mitigate the risk.

There are no known public exploits for this vulnerability at the time of this report. However, it is important to apply the necessary security updates to protect against potential future exploits.

If you encounter any issues during the update process, it is recommended to seek assistance from the Linux Kernel community or consult with a qualified system administrator or security professional.

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