Vulnerability in mxs-saif: Fix refcount leak in mxs_saif_probe

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1003398: ASoC: mxs-saif: Fix refcount leak in mxs_saif_probe. Affects Kernel versions >= 08641c7c74dddfcd726512edfaa3b4cbe42e523e, < 24491124406666bf0dcb9ee10c5575c6ce6a1730. 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 mxs-saif package is a component of the ASoC (Audio System on Chip) framework in the Linux Kernel. It provides support for the i.MX23/i.MX28 SAIF (Serial Audio Interface) controller. The SAIF controller is responsible for handling audio data transmission between the system and audio peripherals. The vulnerability in mxs-saif can lead to a refcount leak in the mxs_saif_probe function.

Vulnerability Detail

The vulnerability in mxs-saif occurs due to a refcount leak in the mxs_saif_probe function. This can result in improper handling of reference counts, leading to memory leaks and potential resource exhaustion. An attacker may be able to exploit this vulnerability to cause a denial-of-service condition or potentially execute arbitrary code with elevated privileges. The vulnerability was introduced in version v3.5 of the Linux Kernel and has been fixed in version v5.15.46.

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 available for this vulnerability. It is recommended to apply the fix mentioned in the 'how_to_fix' section.

Conclusion

The vulnerability in mxs-saif can lead to a refcount leak, potentially causing memory leaks and resource exhaustion. It is crucial to update the Linux Kernel to version v5.15.46 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

mxs-saif is a component of the ASoC framework in the Linux Kernel that provides support for the i.MX23/i.MX28 SAIF controller for audio data transmission.

The vulnerability can lead to a refcount leak, resulting in memory leaks and potential resource exhaustion. It may allow an attacker to cause a denial-of-service condition or execute arbitrary code with elevated privileges.

To fix the vulnerability, update the Linux Kernel to version v5.15.46 or later by obtaining the latest kernel source code and compiling it for the target system.

No, there is no specific workaround available for this vulnerability. Applying the fix mentioned in the 'how_to_fix' section is recommended.

The vulnerability was introduced in version v3.5 of the Linux Kernel and has been fixed in version v5.15.46.

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