Use-after-free vulnerability in moxart package

Kernel Updated 02 Oct 2025

Summary

27/02/2022
N/A
No i
Unrated
Not published

GSD-2022-1000596: moxart: fix potential use-after-free on remove path. Affects Kernel versions < af0e6c49438b1596e4be8a267d218a0c88a42323. 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 moxart package is a component of the Linux Kernel, which is responsible for managing the Moxa ART SoCs. These SoCs are commonly used in industrial control systems and provide various functionalities such as networking, serial communication, and GPIO. The moxart package handles the communication between the hardware and the operating system, ensuring proper operation of the Moxa ART SoCs.

Vulnerability Detail

The identified vulnerability in the moxart package is a use-after-free issue that exists in the remove path. This vulnerability could potentially be exploited by an attacker to execute arbitrary code or cause a denial-of-service condition. The use-after-free vulnerability occurs when a program continues to use a pointer after the memory it points to has been freed, leading to unpredictable behavior and potential security risks. The impact and attack plausibility of this vulnerability have not been proven yet.

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.

Conclusion

The use-after-free vulnerability in the moxart package can be fixed by updating the Linux Kernel to version v5.15.23 or later. It is important to stay up-to-date with security patches to ensure the integrity and security of the system. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

A use-after-free vulnerability occurs when a program continues to use a pointer after the memory it points to has been freed. This can lead to unpredictable behavior and potential security risks.

The impact of this vulnerability could be the execution of arbitrary code or a denial-of-service condition if exploited by an attacker.

No, the impact and attack plausibility of this vulnerability have not been proven yet.

To fix this vulnerability, update the Linux Kernel to version v5.15.23 or later.

No specific workaround has been mentioned for this vulnerability.

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