Memory Leak in mt76: mt7615_unregister_device()

Kernel Updated 02 Oct 2025

Summary

31/05/2021
N/A
No i
Unrated
Not published

GSD-2021-1000236: mt76: mt7615: fix memleak when mt7615_unregister_device(). Affects Kernel versions >= a6275e934605646ef81b02d8d1164f21343149c9, < 6c5b2b0c6e5a6ce2d8f9f85b8b72bfad60eaa506. 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 mt76 package is a driver for MediaTek MT76x0e, MT76x2e, MT7603, MT7615, and MT7663 wireless LAN chipsets. It provides support for these chipsets in the Linux kernel. The mt7615_unregister_device() function is responsible for unregistering a device from the mt7615 driver. However, a memory leak vulnerability has been identified in this function.

Vulnerability Detail

The vulnerability occurs when the mt7615_unregister_device() function is called, leading to a memory leak. This can result in the depletion of system resources over time, potentially causing system instability or denial of service. The vulnerability was introduced in Linux Kernel version v5.12 by commit a6275e934605646ef81b02d8d1164f21343149c9 and was fixed in version v5.12.4 by commit 6c5b2b0c6e5a6ce2d8f9f85b8b72bfad60eaa506.

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

No workaround has been provided for this vulnerability.

Conclusion

The memory leak vulnerability in mt76's mt7615_unregister_device() function can lead to system instability or denial of service. It is crucial to update the Linux Kernel to version v5.12.4 or later to mitigate this vulnerability. For more information and support, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability can lead to a memory leak, potentially causing system instability or denial of service.

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 and Vulert will analyze it for any open-source vulnerabilities, including this one.

There are no known exploits for this vulnerability at the moment. However, it is still important to apply the fix to prevent any potential exploitation in the future.

For further support on vulnerability remediation, you can reach out to info@devnack.com.

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