Vulnerability in Kernel: mmmremap.c

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1001971: mmmremap.c: avoid pointless invalidate_range_start/end on mremap(old_size=0). Affects Kernel versions < 7d659cb1763ff17d1c6ee082fa6feb4267c7a30b. 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, responsible for managing system resources and facilitating communication between hardware and software. It provides essential functionalities for the proper functioning of the system. However, a vulnerability has been identified in the mmmremap.c file, which is part of the Kernel. This vulnerability can potentially lead to security breaches and compromise the integrity of the system.

Vulnerability Detail

The vulnerability in mmmremap.c arises from the improper handling of mremap() calls with old_size=0. This can result in unnecessary invalidate_range_start/end operations, leading to performance degradation and potential security risks. While the exact impact and attack vectors have not been proven, it is crucial to address this vulnerability to ensure the stability and security of the system.

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, if updating the Kernel is not immediately feasible, it is advised to avoid using mremap() calls with old_size=0. By ensuring that the old_size parameter is not set to zero, the vulnerability can be circumvented. Here is an example of how to modify the mremap() call to avoid the issue:

// Original mremap() call
mremap(addr, 0, new_size, MREMAP_MAYMOVE);

// Modified mremap() call
mremap(addr, 1, new_size, MREMAP_MAYMOVE);

Conclusion

In conclusion, the vulnerability in mmmremap.c within the Kernel can potentially lead to performance degradation and security risks. It is crucial to update the Linux Kernel to version v5.10.111 or later to address this issue. Alternatively, a workaround is available by modifying the mremap() call to avoid setting old_size=0. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The Kernel is a critical component of the Linux operating system, responsible for managing system resources and facilitating communication between hardware and software.

mmmremap.c is a file within the Kernel that is involved in memory management operations, including the mremap() system call.

The exact impact of this vulnerability is yet to be proven. However, it can potentially lead to performance degradation and security risks, compromising the stability and integrity of the system.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.10.111 or later, which includes the necessary fix for this issue.

Yes, a workaround is available. By avoiding mremap() calls with old_size=0, the vulnerability can be mitigated. Modify the mremap() call to set the old_size parameter to a non-zero value.

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