kvm: Avoid Speculation-Based Attacks from Out-of-Range Memslot Accesses

Kernel Updated 02 Oct 2025

Summary

30/06/2021
N/A
No i
Unrated
Not published

GSD-2021-1000949: kvm: avoid speculation-based attacks from out-of-range memslot accesses. Affects Kernel versions < 7af299b97734c7e7f465b42a2139ce4d77246975. 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 Kernel package is a critical component of the Linux operating system. It provides the core functionality and interfaces for the system's hardware and software components. The Kernel package is responsible for managing memory, processes, device drivers, and other essential system resources. This vulnerability in the Kernel package allows for speculation-based attacks from out-of-range memslot accesses, potentially leading to unauthorized access, data leakage, or privilege escalation.

Vulnerability Detail

The vulnerability arises from the ability to perform out-of-range memslot accesses in the Kernel package. Attackers can exploit this vulnerability to launch speculation-based attacks, which can bypass security measures and access sensitive information or gain elevated privileges. The impact of such attacks can range from unauthorized access to critical system resources to the leakage of sensitive data. This vulnerability has been addressed in the Linux Kernel version v5.10.44 by commit 7af299b97734c7e7f465b42a2139ce4d77246975.

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. The recommended approach is to apply the fix by updating the Linux Kernel package.

Conclusion

The vulnerability in the Kernel package allows for speculation-based attacks from out-of-range memslot accesses, posing a risk of unauthorized access, data leakage, or privilege escalation. It is crucial to update the Linux Kernel package to version v5.10.44 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability allows for speculation-based attacks from out-of-range memslot accesses, which can lead to unauthorized access, data leakage, or privilege escalation.

You can use tools like Vulert (https://vulert.com) to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities in the software.

At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix promptly to mitigate any potential risks.

Yes, this vulnerability can be exploited remotely if the affected system is accessible over a network. It is crucial to update the Linux Kernel package to prevent any potential remote exploitation.

The recommended solution is to update the Linux Kernel package to the fixed version. However, if updating is not feasible in the short term, implementing additional security measures such as network segmentation and access controls can help mitigate the risk.

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