nitro_enclaves: Use get_user_pages_unlocked() call to handle mmap assert

Kernel Updated 02 Oct 2025

Summary

10/01/2022
N/A
No i
Unrated
Not published

GSD-2022-1000059: nitro_enclaves: Use get_user_pages_unlocked() call to handle mmap assert. Affects Kernel versions >= 5b78ed24e8ec48602c1d6f5a188e58d000c81e2b, < 90d2beed5e753805c5eab656b8d48257638fe543. 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 nitro_enclaves package is a component of the Linux Kernel ecosystem. It provides functionality for creating and managing Nitro Enclaves, which are isolated execution environments for sensitive workloads. Nitro Enclaves utilize hardware-based isolation mechanisms to ensure the security and integrity of the executed code. However, a vulnerability has been discovered in the package that could potentially be exploited by attackers.

Vulnerability Detail

The vulnerability in nitro_enclaves arises from the improper handling of mmap assertions. Specifically, the package does not utilize the get_user_pages_unlocked() call to handle mmap assertions, which can lead to security vulnerabilities. Although the actual impact and attack plausibility have not been proven, it is important to address this vulnerability to ensure the security of Nitro Enclaves. The vulnerability was introduced in version v5.15 of the Linux Kernel and has been fixed in version v5.15.13 by commit 90d2beed5e753805c5eab656b8d48257638fe543.

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 →

Conclusion

In conclusion, the nitro_enclaves package in the Linux Kernel is vulnerable to an issue related to the handling of mmap assertions. This vulnerability can potentially be exploited by attackers, although the actual impact is yet to be proven. To mitigate this vulnerability, it is crucial to update the Linux Kernel to version v5.15.13 or later. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

Nitro Enclaves is a component of the Linux Kernel ecosystem that provides isolated execution environments for sensitive workloads.

The impact of this vulnerability is currently unknown, as the actual attack plausibility has not been proven. However, it is important to address this vulnerability to ensure the security of Nitro Enclaves.

You can use the Vulert Playground at Vulert 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 monitoring and alerts for open-source vulnerabilities.

To update the Linux Kernel, you can follow the official documentation provided by your Linux distribution. This typically involves using package managers or manually compiling and installing the updated Kernel version.

No specific workaround has been mentioned for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.

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