Potential NULL dereference in aspeed_vuart_probe in Kernel

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002994: serial: 8250_aspeed_vuart: Fix potential NULL dereference in aspeed_vuart_probe. Affects Kernel versions >= 54da3e381c2b55289b220601f403f17df7b20597, < 90a6b6fc52bfdcfe9698454bf5bea26112abbcd1. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Kernel is a crucial component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential functionalities and services to enable the proper functioning of the system. The vulnerability in question affects the Kernel's serial driver, specifically the 8250_aspeed_vuart module. This module is responsible for handling serial communication on ASPEED BMC (Baseboard Management Controller) platforms. The vulnerability may lead to a NULL dereference, which can result in a system crash or potential exploitation by an attacker.

Vulnerability Detail

The vulnerability arises from a potential NULL dereference in the aspeed_vuart_probe function of the 8250_aspeed_vuart module. This function is responsible for initializing the ASPEED virtual UART (vUART) device. If a NULL pointer is encountered during the initialization process, it can lead to a system crash or potential security issues. The impact and attack plausibility of this vulnerability have not been proven yet, but it is essential to address it to ensure system stability and security.

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

No workaround has been mentioned for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel to the latest version.

Conclusion

The potential NULL dereference vulnerability in the aspeed_vuart_probe function of the 8250_aspeed_vuart module in the Kernel can lead to system crashes or potential security issues. It is crucial to update the Linux Kernel to version v5.17.15 or later to address this vulnerability. By doing so, the vulnerable code will be replaced with the patched version, ensuring system stability and security. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability can range from a system crash to potential security issues. Exploitation of the NULL dereference could allow an attacker to gain unauthorized access or disrupt the system's normal operation.

You can use tools like Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert Playground allows you to analyze your manifest file, such as package-lock.json, and provides real-time alerts for open-source vulnerabilities.

As of now, there is no known exploit for this vulnerability. However, it is crucial to address it promptly by updating the Linux Kernel to the fixed version to mitigate any potential risks.

The exploitation of this vulnerability requires access to the system and the ability to trigger the vulnerable code path. It is advisable to apply the fix as soon as possible to prevent any potential exploitation.

As there is no specific workaround mentioned for this vulnerability, it is recommended to prioritize updating the Linux Kernel to the fixed version. Applying temporary measures may not provide adequate protection against potential exploitation.

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