Memory Leak in __mdiobus_register in Kernel

Kernel Updated 02 Oct 2025

Summary

14/11/2021
N/A
No i
Unrated
Not published

GSD-2021-1002119: net: mdiobus: Fix memory leak in __mdiobus_register. Affects Kernel versions < 0c4e87ba11eb331dca2315d484d08441b8c13193. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The Kernel is a critical component of the Linux operating system that manages communication between hardware and software. It provides essential services and functions for the proper functioning of the system. The __mdiobus_register function is part of the mdiobus subsystem in the Kernel, which handles management of the Media Independent Interface (MII) buses. MII buses are used for communication between Ethernet PHYs and network controllers. This vulnerability in __mdiobus_register can lead to a memory leak, potentially causing resource exhaustion and system instability.

Vulnerability Detail

The vulnerability in __mdiobus_register arises from a memory leak issue. When registering a new MII bus, the function fails to release allocated memory in certain error paths. As a result, memory resources are not properly freed, leading to a memory leak. An attacker could potentially exploit this vulnerability to exhaust system memory, causing denial-of-service conditions or other unpredictable behavior. It is important to note that the impact and attack plausibility of this vulnerability have not been proven.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.14.15 or later. This fix is implemented in commit 0c4e87ba11eb331dca2315d484d08441b8c13193. Updating the Kernel to the latest stable version ensures that the memory leak issue in __mdiobus_register is addressed.

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. However, applying the recommended fix by updating the Kernel to the latest stable version is the best course of action.

Conclusion

In conclusion, the vulnerability in __mdiobus_register in the Kernel can lead to memory leaks, potentially causing resource exhaustion and system instability. It is crucial to update the Kernel to version v5.14.15 or later to fix this vulnerability. Applying the recommended fix ensures that the memory leak issue is addressed. For more information and support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability could potentially lead to resource exhaustion and system instability due to memory leaks. However, the actual impact and attack plausibility have not been proven.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.

There are no known exploits for this vulnerability at the moment. However, it is always recommended to apply security updates and patches to mitigate potential risks.

For more details about this vulnerability, you can refer to the source link provided in the vulnerability details section of the Open Source Vulnerability format.

For further support on vulnerability remediation, you can reach out to info@devnack.com. They can provide assistance and guidance in addressing this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.14.15 or later. This fix is implemented in commit 0c4e87ba11eb331dca2315d484d08441b8c13193. Updating the Kernel to the latest stable version ensures that the memory leak issue in __mdiobus_register is addressed.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.