KVM: x86: Fix stack-out-of-bounds memory access from ioapic_write_indirect() in Kernel

Kernel Updated 02 Oct 2025

Summary

19/10/2021
N/A
No i
Unrated
Not published

GSD-2021-1001730: KVM: x86: Fix stack-out-of-bounds memory access from ioapic_write_indirect(). Affects Kernel versions >= 7ee30bc132c683d06a6d9e360e39e483e3990708, < 99a9e9b80f19fc63be005a33d76211dd23114792. 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 Kernel is a fundamental component of the Linux operating system that provides core functionalities and interfaces between hardware and software. It manages system resources, facilitates communication between processes, and handles device drivers. The Kernel is responsible for the overall stability and security of the operating system. However, a vulnerability has been identified in the Kernel that could potentially lead to a stack-out-of-bounds memory access when executing the ioapic_write_indirect() function.

Vulnerability Detail

The vulnerability arises from a stack-out-of-bounds memory access in the ioapic_write_indirect() function within the x86 implementation of the Kernel's KVM (Kernel-based Virtual Machine) subsystem. This vulnerability can be exploited by an attacker to gain unauthorized access or execute arbitrary code on the affected system. The issue was introduced in version v5.5 of the Linux Kernel and has been fixed in version v5.14.10. The impact and attack plausibility of this vulnerability have not been proven yet, but it is crucial to address it to ensure the security of the system.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.14.10 or later. This update includes the necessary patch to address the stack-out-of-bounds memory access issue in the ioapic_write_indirect() function. Updating the Kernel will ensure that the system is protected against potential exploitation of 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 apply the patch manually to the affected Kernel version. The patch can be obtained from the Linux Kernel repository at: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/. However, it is strongly advised to update to the latest stable version of the Kernel to benefit from comprehensive security fixes and improvements.

Conclusion

The identified vulnerability in the Kernel's KVM subsystem poses a potential risk of unauthorized access or execution of arbitrary code. It is crucial to update the Linux Kernel to version v5.14.10 or later to mitigate this vulnerability. Applying the provided patch manually or using package managers to update the Kernel will ensure the system's security. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability is not yet proven, but it has the potential to allow unauthorized access or execution of arbitrary code on the affected system.

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 analyze and alert you in real-time if the vulnerability is present.

Yes, a workaround is available. Users can manually apply the patch provided by the Linux Kernel repository to the affected version. However, it is recommended to update to the latest stable version of the Kernel for comprehensive security fixes.

You can find more information about this vulnerability in the GSD-2021-1001730 entry of the GSD database maintained by the Cloud Security Alliance. The entry can be accessed at: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1001xxx/GSD-2021-1001730.json

To update the Linux Kernel, you can follow the official documentation provided by your Linux distribution. Typically, it involves using package managers like apt, yum, or dnf to install the latest Kernel version available for your distribution.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.14.10 or later. This update includes the necessary patch to address the stack-out-of-bounds memory access issue in the ioapic_write_indirect() function. Updating the Kernel will ensure that the system is protected against potential exploitation of 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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.