Critical Vulnerability in Linux Kernel: KVM Cache Management Flaw

linux Updated 02 Oct 2025

Summary

01/05/2025
N/A
Yes i
Unrated
Not published

CVE-2022-49882: In the Linux kernel, the following vulnerability has been resolved: KVM: Reject attempts to consume or refresh inactive gfn_to_pfn_cache Reject kvm_gpc_check() and kvm_gpc_refresh() if the cache is inactive. Affects linux versions < 6.0.8-1. Fixed in 6.0.8-1. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Linux kernel is a core component of many operating systems, providing essential services for hardware and software interaction. It is known for its robustness and flexibility, supporting a wide range of devices and architectures. However, the kernel's complexity can lead to vulnerabilities, such as the one identified in the KVM (Kernel-based Virtual Machine) subsystem, which is responsible for virtualization. This specific vulnerability affects the cache management of KVM, potentially leading to severe security issues.

Vulnerability Detail

In the Linux kernel, a vulnerability has been identified in the KVM subsystem related to the handling of the gfn_to_pfn_cache. The issue arises when attempts are made to consume or refresh an inactive cache, which can lead to use-after-free bugs. This occurs because the active flag is not checked during the refresh process, allowing KVM to operate with a valid but inactive cache. This flaw can result in critical failures, such as dereferencing a NULL kernel pointer or failing to invalidate memory mappings, which can be exploited through a race condition between specific KVM ioctl commands.

How To Fix

Minimum fixed version

6.0.8-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. The best course of action is to apply the available patch by updating the kernel to the fixed version.

Conclusion

The identified vulnerability in the Linux kernel's KVM subsystem poses significant risks due to improper cache management. Users are strongly advised to update their systems to the latest patched version to mitigate these risks. Utilizing tools like Vulert can further enhance security by providing real-time monitoring for open-source vulnerabilities.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

The vulnerability involves improper handling of the KVM cache, which can lead to use-after-free bugs and potential system crashes.

You can use Vulert, which monitors open-source vulnerabilities in your software. By uploading a manifest file like package-lock.json, you can check for vulnerabilities without needing to install any software.

Exploiting this vulnerability can lead to system instability, crashes, and potential unauthorized access to system resources.

Yes, updating to version 6.0.8-1 or later will resolve the vulnerability.

Using tools like Vulert can help you monitor for vulnerabilities in real-time, ensuring that you are alerted to any new issues as they arise.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

Minimum fixed version

6.0.8-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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