net/mlx5e: Nullify cq->dbg pointer in mlx5_debug_cq_remove()

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1002285: net/mlx5e: nullify cq->dbg pointer in mlx5_debug_cq_remove(). Affects Kernel versions >= 4f7bddf8c5c01cac74373443b13a68e1c6723a94, < 471c492890557bd58f73314bb4ad85d5a8fd5026. 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 net/mlx5e package is a network driver for Mellanox ConnectX-4 and ConnectX-5 Ethernet adapters. It provides support for various features and optimizations specific to these adapters. The mlx5_debug_cq_remove() function is responsible for removing a debug entry from the completion queue (cq) of the network adapter. This function is vulnerable to a null pointer dereference issue.

Vulnerability Detail

The vulnerability arises from the failure to nullify the cq->dbg pointer in the mlx5_debug_cq_remove() function. This can lead to a null pointer dereference when attempting to access the debug entry, resulting in a system crash or potential privilege escalation. An attacker with local access to the system may be able to exploit this vulnerability to gain elevated privileges or disrupt the normal operation of the network adapter.

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.10.82 or later. This fix can be obtained by applying commit 471c492890557bd58f73314bb4ad85d5a8fd5026. It is important to ensure that the updated kernel is properly tested and deployed to all affected systems.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the fix mentioned in the 'how_to_fix' section.

Conclusion

The net/mlx5e package is vulnerable to a null pointer dereference issue in the mlx5_debug_cq_remove() function. This vulnerability can lead to system crashes or potential privilege escalation. It is crucial to update the Linux Kernel to version v5.10.82 or later to fix this vulnerability. No known workarounds are available. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can result in a system crash or potential privilege escalation. An attacker with local access to the system may be able to exploit this vulnerability to gain elevated privileges or disrupt the normal operation of the network adapter.

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 to the playground and it will provide real-time alerts for open-source vulnerabilities.

There is no known workaround for this vulnerability. It is recommended to apply the fix mentioned in the 'how_to_fix' section.

There are no known exploits for this vulnerability at the moment. However, it is important to apply the fix as soon as possible to mitigate the risk.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

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.10.82 or later. This fix can be obtained by applying commit 471c492890557bd58f73314bb4ad85d5a8fd5026. It is important to ensure that the updated kernel is properly tested and deployed to all affected systems.

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.