Use-after-free vulnerability in moxart package

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1000236: moxart: fix potential use-after-free on remove path. Affects Kernel versions < be93028d306dac9f5b59ebebd9ec7abcfc69c156. 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 moxart package is a component of the Linux Kernel, which is responsible for managing the Moxa ART SoC devices. These devices are used in various industrial applications and provide features such as serial communication, GPIO, and interrupt handling. The moxart package is critical for the proper functioning of these devices and is widely used in industrial systems.

Vulnerability Detail

The identified vulnerability in the moxart package is a potential use-after-free issue on the remove path. This vulnerability could allow an attacker to exploit a freed memory region, leading to various security risks. The impact and attack plausibility of this vulnerability have not been proven yet, but it is crucial to address it to ensure the security of systems utilizing the moxart package.

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 →

Conclusion

The use-after-free vulnerability in the moxart package poses a potential security risk to systems utilizing Moxa ART SoC devices. It is recommended to update the Linux Kernel to version v5.10.100 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The moxart package is a component of the Linux Kernel that manages Moxa ART SoC devices used in industrial applications.

A use-after-free vulnerability occurs when a program continues to use a memory region after it has been freed, leading to potential security risks.

If exploited, this vulnerability could allow an attacker to execute arbitrary code or cause a denial-of-service condition on systems utilizing the moxart package.

No, the impact and attack plausibility of this vulnerability have not been proven yet. However, it is still important to address it to ensure system security.

To fix this vulnerability, update the Linux Kernel to version v5.10.100 or later, which includes the necessary fix for the use-after-free issue.

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