Memory Leak Vulnerability in Linux Kernel

Kernel Updated 02 Oct 2025

Summary

27/02/2022
N/A
No i
Unrated
Not published

GSD-2022-1000375: net: fix a memleak when uncloning an skb dst and its metadata. Affects Kernel versions >= fc4099f17240767554ff3a73977acb78ef615404, < 00e6d6c3bc14dfe32824e2c515f0e0f2d6ecf2f1. 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 Linux Kernel is the core component of the Linux operating system, responsible for managing system resources and providing essential services. It is an open-source project that has a large community of developers contributing to its development and maintenance. The vulnerability in question relates to the handling of skb dst and its metadata, which can lead to a memory leak. skb dst is a data structure used in networking subsystems to store information about the destination of a network packet. A memory leak occurs when memory is allocated but not properly deallocated, leading to a gradual depletion of available memory resources.

Vulnerability Detail

The vulnerability arises when uncloning an skb dst and its metadata. This can result in a memory leak, where memory allocated for the skb dst and its metadata is not properly freed. An attacker could potentially exploit this vulnerability to exhaust system memory resources, leading to a denial-of-service condition. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in version v4.3 of the Linux Kernel and has been fixed in version v5.10.101 by commit 00e6d6c3bc14dfe32824e2c515f0e0f2d6ecf2f1.

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 mentioned for this vulnerability.

Conclusion

The memory leak vulnerability in the Linux Kernel, specifically related to uncloning an skb dst and its metadata, can potentially lead to a denial-of-service condition by depleting system memory resources. It is crucial to update the Linux Kernel to version v5.10.101 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability is a potential memory leak, which can lead to a gradual depletion of available system memory resources and potentially result in a denial-of-service condition.

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 is no information available regarding exploitation of this vulnerability in the wild.

The recommended mitigation is to update the Linux Kernel to the fixed version, as mentioned in the 'how_to_fix' section.

The discoverer of this vulnerability is not mentioned in the provided information.

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