pinctrl: aspeed: Fix 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-1004558: pinctrl: aspeed: Fix potential NULL dereference in aspeed_pinmux_set_mux(). Affects Kernel versions < ef1e38532f4b2f0f3b460e938a2e7076c3bed5ee. 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-aspeed driver is responsible for managing pin control and pinmuxing on ASPEED SoCs. It provides an interface for configuring and controlling the multiplexing of pins on ASPEED chips. The aspeed_pinmux_set_mux() function is a key component of this driver and is used to set the pinmux configuration for a specific pin. However, there is a potential NULL dereference vulnerability in this function that could lead to a system crash or other unpredictable behavior.

Vulnerability Detail

The vulnerability arises from a lack of proper validation of the 'pctldev' parameter in the aspeed_pinmux_set_mux() function. If this parameter is NULL, the function attempts to dereference it, leading to a NULL pointer dereference. An attacker could potentially exploit this vulnerability by supplying a crafted input that triggers the NULL dereference, resulting in a denial of service (system crash) or other unexpected behavior. The impact and attack plausibility of this vulnerability have not been proven yet.

How To Fix

No fixed version is published for this vulnerability.

The vulnerability has been fixed in Linux Kernel version v5.10.132 by commit ef1e38532f4b2f0f3b460e938a2e7076c3bed5ee. To fix the vulnerability, users should update their kernel to a version that includes this commit. It is recommended to regularly update the kernel to the latest stable version to ensure all security fixes are applied.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. Updating the kernel to a version that includes the fix is the recommended solution.

Conclusion

The pinctrl-aspeed driver in the Linux Kernel is vulnerable to a potential NULL dereference in the aspeed_pinmux_set_mux() function. This vulnerability has been fixed in Linux Kernel version v5.10.132. Users are advised to update their kernel to a version that includes the fix to ensure the security of their systems. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The pinctrl-aspeed driver is responsible for managing pin control and pinmuxing on ASPEED SoCs. It provides an interface for configuring and controlling the multiplexing of pins on ASPEED chips.

The impact of this vulnerability is not yet proven. It could potentially lead to a system crash or other unexpected behavior.

An attacker could potentially exploit this vulnerability by supplying a crafted input that triggers the NULL dereference, resulting in a denial of service (system crash) or other unexpected behavior.

Yes, this vulnerability has been fixed in Linux Kernel version v5.10.132 by commit ef1e38532f4b2f0f3b460e938a2e7076c3bed5ee.

To fix this vulnerability, users should update their kernel to a version that includes the fix. It is recommended to regularly update the kernel to the latest stable version.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

The vulnerability has been fixed in Linux Kernel version v5.10.132 by commit ef1e38532f4b2f0f3b460e938a2e7076c3bed5ee. To fix the vulnerability, users should update their kernel to a version that includes this commit. It is recommended to regularly update the kernel to the latest stable version to ensure all security fixes are applied.

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.