Memory Leak in mkiss_close in Kernel

Kernel Updated 02 Oct 2025

Summary

30/06/2021
N/A
No i
Unrated
Not published

UVI-2021-1000989: net: hamradio: fix memory leak in mkiss_close. Affects Kernel versions >= 815f62bf742718458ba822a7e1f51f285eb997f2, < 290b0b6432e2599021db0b8d6046f756d931c29f. 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 Kernel is a critical component of the Linux operating system that provides core functionalities and interfaces between hardware and software. It is responsible for managing system resources, including memory, processes, and device drivers. The mkiss_close function is part of the hamradio network subsystem in the Kernel, which handles communication over amateur radio protocols. This vulnerability specifically affects the mkiss_close function, leading to a memory leak.

Vulnerability Detail

The mkiss_close function in the hamradio network subsystem of the Kernel suffers from a memory leak. When this function is called to close a mkiss device, it fails to release allocated memory, resulting in a gradual depletion of system resources. An attacker could potentially exploit this vulnerability to exhaust available memory, leading to system instability or denial of service. The vulnerability was introduced in Kernel version 2.6.14 and is fixed in version 5.10.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

As a temporary workaround, users can avoid using the affected hamradio network subsystem or disable the mkiss functionality if not required. This can be achieved by unloading the corresponding Kernel module or blacklisting it to prevent it from being loaded during system startup. The specific steps to perform this workaround may vary depending on the Linux distribution and the system's configuration.

Conclusion

The memory leak vulnerability in the mkiss_close function of the hamradio network subsystem in the Kernel can lead to system instability or denial of service. It is crucial to update the Linux Kernel to version 5.10.46 or later to fix this vulnerability. Users can also employ temporary workarounds, such as avoiding the affected subsystem or disabling the mkiss functionality. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability can lead to a gradual depletion of system resources, 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 the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.

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

No, this vulnerability requires local access to the system in order to exploit it.

The recommended solution is to update the Linux Kernel to the fixed version. However, if updating the Kernel is not feasible, you can consider implementing strict resource limits or monitoring mechanisms to detect and mitigate excessive resource consumption.

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