Vulnerability in ASoC: mxs-saif

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1003610: ASoC: mxs-saif: Fix refcount leak in mxs_saif_probe. Affects Kernel versions >= 08641c7c74dddfcd726512edfaa3b4cbe42e523e, < 2a0da7641e1f17a744ac7b3f76471388c97b63dc. 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 ASoC (Audio System on Chip) framework in the Linux Kernel provides support for audio drivers on various embedded systems. One of the supported drivers is mxs-saif, which is responsible for handling audio input and output on MXS (i.MX23/i.MX28) based platforms. However, a vulnerability has been discovered in the mxs-saif driver that can lead to a reference count leak.

Vulnerability Detail

The vulnerability in mxs-saif driver, identified as GSD-2022-1003610, occurs during the probe process. When the driver is initialized, a reference count is incremented. However, under certain conditions, this reference count is not properly decremented, leading to a refcount leak. Although the impact and attack plausibility of this vulnerability have not been proven, it is important to address it to maintain the integrity and security of the system.

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 vulnerability in the mxs-saif driver can result in a refcount leak, potentially leading to resource management issues or memory leaks. To mitigate this vulnerability, it is recommended to update the Linux Kernel to version v5.10.121 or later. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

ASoC stands for Audio System on Chip. It is a framework in the Linux Kernel that provides support for audio drivers on embedded systems.

mxs-saif is an audio driver supported by the ASoC framework. It is responsible for handling audio input and output on MXS (i.MX23/i.MX28) based platforms.

A refcount leak occurs when the reference count of a resource is not properly decremented, leading to a memory leak or other resource management issues.

The impact of this vulnerability is not proven, but it could potentially lead to resource management issues or memory leaks in the mxs-saif driver.

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 to the playground, and it will alert you in real-time if your application is affected.

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