Out-of-Bounds Memory Access in mlxsw: thermal

Kernel Updated 02 Oct 2025

Summary

28/10/2021
N/A
No i
Unrated
Not published

GSD-2021-1001853: mlxsw: thermal: Fix out-of-bounds memory accesses. Affects Kernel versions >= a50c1e35650b929500bd89be61c89d95a267ce56, < e59d839743b50cb1d3f42a786bea48cc5621d254. 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

The mlxsw: thermal vulnerability affects the Kernel package in the Linux ecosystem. The Kernel package is a critical component of the Linux operating system, responsible for managing core system functions and providing an interface between hardware and software. The mlxsw: thermal module within the Kernel package is specifically responsible for thermal management of Mellanox Switch devices. This vulnerability allows for out-of-bounds memory accesses, which can lead to various security issues and system instability.

Vulnerability Detail

The mlxsw: thermal vulnerability arises from out-of-bounds memory accesses. This occurs when the mlxsw: thermal module attempts to access memory beyond the boundaries of an allocated buffer. An attacker could exploit this vulnerability to read sensitive information from kernel memory or modify critical data structures, potentially leading to privilege escalation, denial of service, or other security compromises. The vulnerability was introduced in version v4.10 of the Linux Kernel and has been fixed in version v5.10.75.

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

No specific workaround has been mentioned for this vulnerability.

Conclusion

The mlxsw: thermal vulnerability in the Kernel package exposes systems to potential security risks and instability. It is crucial to update to the fixed version of the Linux Kernel (v5.10.75 or later) to mitigate this vulnerability. For further support and assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The mlxsw: thermal vulnerability can potentially lead to privilege escalation, denial of service, or other security compromises. It allows an attacker to read sensitive information from kernel memory or modify critical data structures.

You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just a manifest file like package-lock.json.

Yes, the vulnerability has been fixed in version v5.10.75 of the Linux Kernel. It is recommended to update to this version or a later one to apply the patch.

The recommended approach is to update the Linux Kernel to the fixed version. However, if updating is not immediately feasible, it is advisable to follow general security best practices, such as restricting access to vulnerable systems, implementing network segmentation, and monitoring for any suspicious activities.

You can refer to the vulnerability details in the GSD database maintained by the Cloud Security Alliance. The specific vulnerability ID is GSD-2021-1001853, and the source can be found at: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1001xxx/GSD-2021-1001853.json

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