Memory Leak in RDMA/mlx5

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1001838: RDMA/mlx5: Fix memory leak in error flow for subscribe event routine. Affects Kernel versions >= 7597385371425febdaa8c6a1da3625d4ffff16f5, < 8dd392e352d3269938fea32061a74655a613f929. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

RDMA/mlx5 is a component of the Linux Kernel that provides support for Remote Direct Memory Access (RDMA) over Mellanox ConnectX-4 and ConnectX-5 adapters. RDMA allows for high-speed, low-latency communication between remote systems. The mlx5 driver is responsible for managing the Mellanox ConnectX-4 and ConnectX-5 adapters and enabling RDMA functionality. However, a memory leak vulnerability has been discovered in the error flow for the subscribe event routine of RDMA/mlx5.

Vulnerability Detail

The vulnerability in RDMA/mlx5's subscribe event routine can lead to a memory leak. When an error occurs during the event subscription process, memory allocated for the event subscription is not properly freed, resulting in a memory leak. An attacker could potentially exploit this vulnerability to exhaust system memory resources, leading to a denial-of-service condition. The vulnerability was introduced in version v5.3 of the Linux Kernel and has been fixed in version v5.15.33.

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 provided for this vulnerability. The recommended solution is to update the Linux Kernel to the fixed version.

Conclusion

The memory leak vulnerability in RDMA/mlx5's subscribe event routine can be addressed by updating the Linux Kernel to version v5.15.33 or later. This update includes the necessary patch to fix the memory leak issue and ensure proper management of system memory resources. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

RDMA/mlx5 is a component of the Linux Kernel that enables Remote Direct Memory Access (RDMA) over Mellanox ConnectX-4 and ConnectX-5 adapters. It allows for high-speed, low-latency communication between remote systems.

The vulnerability in RDMA/mlx5's subscribe event routine can result in a memory leak, potentially leading to a denial-of-service condition by exhausting system memory resources.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.15.33 or later, which includes the necessary patch to address the memory leak issue.

No specific workaround is provided for this vulnerability. Updating the Linux Kernel to the fixed version is the recommended solution.

The vulnerability was introduced in version v5.3 of the Linux Kernel and has been fixed in version v5.15.33.

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