ARM: mmp: Fix failure to remove sram device in Kernel

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002039: ARM: mmp: Fix failure to remove sram device. Affects Kernel versions < e7bb29df2a149f466c660209ea1aa3783b3e0e1c. 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 Kernel is a crucial component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential services, such as managing system resources, handling device drivers, and facilitating communication between different software components. The vulnerability in question affects the ARM mmp module within the Kernel. The ARM mmp module is responsible for managing the system's memory and peripheral devices. This vulnerability specifically relates to the failure to remove the sram device, which can have security implications.

Vulnerability Detail

The vulnerability arises from a flaw in the ARM mmp module, which results in the failure to remove the sram device. This issue can potentially be exploited by an attacker to gain unauthorized access to sensitive information or execute arbitrary code. The impact and attack plausibility of this vulnerability have not been proven yet. It is important to note that this vulnerability has been addressed in the Linux Kernel version v5.10.110 by commit e7bb29df2a149f466c660209ea1aa3783b3e0e1c.

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 workaround, users can disable the sram device manually by modifying the Kernel configuration. This can be achieved by removing the relevant configuration options related to the sram device from the Kernel configuration file and recompiling the Kernel. However, this workaround is not recommended as it may have unintended consequences and is not a permanent solution.

Conclusion

In conclusion, the ARM mmp module in the Kernel is vulnerable to a failure to remove the sram device, which can have security implications. It is crucial to update the Linux Kernel to version v5.10.110 or later to mitigate this vulnerability. Alternatively, users can disable the sram device manually as a temporary workaround. For further assistance and support in addressing this vulnerability, please reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability can vary depending on the specific system and its usage. However, potential consequences include unauthorized access to sensitive information and the execution of arbitrary code.

There is no evidence to suggest that this vulnerability has been exploited in real-world scenarios. However, it is always recommended to apply security patches promptly to mitigate potential risks.

No, this vulnerability has been fixed in the Linux Kernel version v5.10.110 and later. It is advisable to update to the latest stable version to ensure the security of the system.

No, the fix for this vulnerability requires updating the entire Kernel to version v5.10.110 or later. It is not possible to apply the fix selectively without updating the entire Kernel.

For more details about this vulnerability, including the technical aspects and the fix, you can refer to the source link provided in the vulnerability details section.

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