Vulnerability in ASoC: mxs-saif

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1004012: ASoC: mxs-saif: Fix refcount leak in mxs_saif_probe. Affects Kernel versions >= 08641c7c74dddfcd726512edfaa3b4cbe42e523e, < d42601e93fce7802bb8d70dd59b60cfeefa20469. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The ASoC (Audio System on Chip) framework in the Linux Kernel provides support for audio devices integrated into system-on-chip (SoC) platforms. One of the components in the ASoC framework is mxs-saif, which is responsible for handling audio data on the MXS (i.MX23/i.MX28) SoC family. The mxs-saif driver allows audio input and output through the SAIF (Serial Audio Interface) peripheral. However, a vulnerability has been discovered in the mxs-saif driver that can lead to a reference count leak during the probe process.

Vulnerability Detail

The vulnerability in mxs-saif driver arises from a refcount leak in the mxs_saif_probe function. When the mxs_saif_probe function is called, it increments the reference count of the device. However, if an error occurs during the probe process, the reference count is not properly decremented, leading to a refcount leak. This refcount leak can result in resource exhaustion and potential denial-of-service conditions. The vulnerability was introduced in Linux Kernel version v3.5 by commit 08641c7c74dddfcd726512edfaa3b4cbe42e523e and has been fixed in version v4.14.283 by commit d42601e93fce7802bb8d70dd59b60cfeefa20469.

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 vulnerability in the mxs-saif driver can lead to resource exhaustion and potential denial-of-service conditions. It is recommended to update the Linux Kernel to version v4.14.283 or later to fix this vulnerability. Stay updated with the official Linux Kernel security advisories for any future patches or updates related to the mxs-saif driver. 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 devices integrated into system-on-chip (SoC) platforms.

mxs-saif is a component in the ASoC framework responsible for handling audio data on the MXS (i.MX23/i.MX28) SoC family. It allows audio input and output through the SAIF (Serial Audio Interface) peripheral.

A refcount leak occurs when the reference count of a resource is not properly decremented, leading to a leak of resources. In this vulnerability, a refcount leak happens during the mxs_saif_probe function, potentially resulting in resource exhaustion and denial-of-service conditions.

The vulnerability can lead to resource exhaustion and potential denial-of-service conditions. An attacker may be able to exploit this vulnerability to exhaust system resources, causing the affected system to become unresponsive or crash.

You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities in the software, without requiring access to the code or installation.

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