Vulnerability in Kernel package: iommu/mediatek: Remove clk_disable in mtk_iommu_remove

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1003324: iommu/mediatek: Remove clk_disable in mtk_iommu_remove. Affects Kernel versions >= b34ea31fe013569d42b7e8681ef3f717f77c5b72, < 053465ab20dcd324a43a1811ee98e5721e6a3e65. 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 Kernel package is a crucial component of the Linux operating system, responsible for managing the system's core functionality. It provides an interface between the hardware and software layers, allowing applications to communicate with the underlying hardware. The iommu/mediatek module within the Kernel package specifically handles input-output memory management unit (IOMMU) operations for MediaTek devices. The IOMMU is responsible for mapping virtual addresses to physical addresses, ensuring secure and efficient data transfers. However, a vulnerability has been identified in the iommu/mediatek module, which may lead to potential security risks.

Vulnerability Detail

The vulnerability in the iommu/mediatek module involves the improper handling of clock resources during the removal of the MediaTek IOMMU driver (mtk_iommu_remove). Specifically, the clk_disable function is called without proper synchronization, potentially resulting in a use-after-free scenario. An attacker could exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition. This vulnerability was introduced in Linux Kernel version v5.13 and has been fixed in 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

If updating the Linux Kernel package is not immediately feasible, a potential workaround is to avoid removing the MediaTek IOMMU driver (mtk_iommu_remove) while the system is in use. By keeping the driver loaded, the vulnerability can be mitigated. However, this workaround may not be suitable for all scenarios and it is strongly recommended to apply the official fix as soon as possible.

Conclusion

The vulnerability in the iommu/mediatek module of the Kernel package poses a potential security risk, allowing for arbitrary code execution or denial-of-service attacks. It is crucial to update the Linux Kernel package to version v5.15.46 or later, which includes the necessary fix. If immediate updating is not possible, it is advised to keep the MediaTek IOMMU driver loaded as a temporary workaround. For further assistance or support in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability may allow an attacker to execute arbitrary code or cause a denial-of-service condition on systems utilizing the vulnerable version of the Kernel package.

You can use the Vulert 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 provide real-time alerts for open-source vulnerabilities.

At the time of this report, there is no known public exploit for this vulnerability. However, it is important to apply the fix promptly to mitigate any potential risks.

Yes, this vulnerability can be exploited remotely if the affected system is exposed to malicious actors over a network connection.

In addition to applying the fix for this vulnerability, it is always recommended to follow best practices for system security, such as keeping software up to date, implementing strong access controls, and regularly monitoring for any suspicious activity.

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