Vulnerability in pinctrl: aspeed package - Potential NULL Dereference in aspeed_pinmux_set_mux()

Kernel Updated 02 Oct 2025

Summary

31/07/2022
N/A
No i
Unrated
Not published

GSD-2022-1004161: pinctrl: aspeed: Fix potential NULL dereference in aspeed_pinmux_set_mux(). Affects Kernel versions < e162a24f1dd06c0dcae71f2565c9f3da2827b98e. 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: aspeed package is a component of the Linux Kernel that provides pin control and pinmux functionality for ASPEED SoCs. It allows for the configuration of pin multiplexing, which determines the function of each pin on the system. This package is widely used in systems utilizing ASPEED SoCs, such as servers, networking devices, and embedded systems. However, a potential vulnerability has been identified in the aspeed_pinmux_set_mux() function, which could lead to a NULL dereference.

Vulnerability Detail

The vulnerability arises from a potential NULL dereference in the aspeed_pinmux_set_mux() function within the pinctrl: aspeed package. If a certain condition is met, the function may attempt to dereference a NULL pointer, leading to a system crash or potential code execution. The impact and attack plausibility of this vulnerability have not been proven, but it is crucial to address it to ensure system stability and security. The vulnerability has been fixed in Linux Kernel version v5.18.13 by commit e162a24f1dd06c0dcae71f2565c9f3da2827b98e.

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 mentioned for this vulnerability. It is advised to apply the fix by updating the Linux Kernel as mentioned in the 'how_to_fix' section.

Conclusion

The pinctrl: aspeed package in the Linux Kernel is vulnerable to a potential NULL dereference in the aspeed_pinmux_set_mux() function. To mitigate this vulnerability, it is crucial to update the Linux Kernel to version v5.18.13 or later. This will ensure system stability and security. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The pinctrl: aspeed package is a component of the Linux Kernel that provides pin control and pinmux functionality for ASPEED SoCs.

Pin multiplexing refers to the configuration of pins on a system to perform different functions based on the desired functionality.

A NULL dereference occurs when a program attempts to access or manipulate memory using a pointer that is not pointing to a valid memory location (i.e., NULL). This can lead to crashes or potential code execution.

The potential ramifications of this vulnerability include system crashes, instability, or potential code execution, depending on the specific conditions and attacker capabilities.

You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will analyze it for any open-source vulnerabilities, including this one.

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