Vulnerability in Linux Kernel: mmmremap.c

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002396: mmmremap.c: avoid pointless invalidate_range_start/end on mremap(old_size=0). Affects Kernel versions < eeaf28e2a0128147d687237e59d5407ee1b14693. 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 Linux Kernel is the core component of the Linux operating system, responsible for managing system resources and providing essential functionality. The mmmremap.c file is part of the kernel and is used for memory management operations, specifically the mremap() function. This vulnerability in mmmremap.c can lead to unnecessary invalidate_range_start/end calls when the old_size parameter is set to 0. These unnecessary calls can impact system performance and potentially introduce security risks.

Vulnerability Detail

The vulnerability in mmmremap.c arises from the improper handling of the mremap() function when the old_size parameter is set to 0. This can result in unnecessary invalidate_range_start/end calls, which can have performance implications. While the actual impact and attack plausibility have not been proven, it is important to address this vulnerability to ensure optimal system performance and mitigate potential security risks.

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 mentioned for this vulnerability.

Conclusion

The vulnerability in mmmremap.c of the Linux Kernel can lead to unnecessary invalidate_range_start/end calls, impacting system performance and potentially introducing security risks. It is crucial to update the kernel to version v4.14.276 or later to fix this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability can vary, but it primarily affects system performance due to unnecessary invalidate_range_start/end calls. There is also a potential for security risks, although the exact attack vectors and consequences have not been proven.

You can use tools like Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert Playground allows you to analyze your application's manifest file, such as package-lock.json, without requiring code access or installation.

At the time of this report, there is no known exploit for this vulnerability. However, it is still important to address it by updating the Linux Kernel to the fixed version.

While the primary risk is related to system performance, there is a possibility that attackers could leverage this vulnerability to launch other attacks. It is always recommended to keep your system up to date with the latest security patches.

As there is no specific workaround mentioned for this vulnerability, the best course of action is to update the Linux Kernel to the fixed version as soon as possible.

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