Kernel Vulnerability in Linux Package: virtio Device Handling Issue

linux Updated 02 Oct 2025

Summary

26/02/2025
N/A
Yes i
Unrated
Not published

CVE-2022-49146: In the Linux kernel, the following vulnerability has been resolved: virtio: use virtio_device_ready() in virtio_device_restore() After waking up a suspended VM, the kernel prints the following trace for virtio drivers wh... Affects linux versions < 5.17.3-1. Fixed in 5.17.3-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 the core component of many operating systems, providing essential services for hardware management and system operations. It supports various drivers, including virtio, which is designed for efficient virtualization. This vulnerability affects the virtio drivers, particularly in how they handle device readiness during the restoration of suspended virtual machines, potentially leading to improper interrupt handling.

Vulnerability Detail

The vulnerability, identified as CVE-2022-49146, arises from the failure of certain virtio drivers to call the virtio_device_ready() function during the .restore process after a virtual machine wakes up from suspension. This oversight can result in kernel warnings and improper interrupt management, as the .enable_cbs callback is not invoked, leading to potential system instability and degraded performance. The kernel logs may show traces indicating that interrupts were not properly handled, which can affect the overall functionality of the virtualized environment.

How To Fix

Minimum fixed version

5.17.3-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 as soon as possible.

Conclusion

The CVE-2022-49146 vulnerability in the Linux kernel's virtio drivers poses a risk of improper interrupt handling after a virtual machine resumes from suspension. Users are strongly advised to update to the patched version 5.17.3-1 or later to mitigate this issue. Monitoring tools like Vulert can assist in identifying vulnerabilities in your software.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

CVE-2022-49146 is a vulnerability in the Linux kernel related to virtio drivers that can lead to improper interrupt handling after a virtual machine resumes from suspension.

This vulnerability can cause kernel warnings and may lead to system instability or degraded performance in virtualized environments using virtio drivers.

Yes, a patch is available in version 5.17.3-1 of the Linux package. Users should update to this version or later to mitigate the vulnerability.

While there are no specific workarounds, it is crucial to plan for an update as soon as possible to ensure system stability and security.

You can use Vulert, which monitors open-source vulnerabilities in your software using a manifest file like package-lock.json. You can check for vulnerabilities in your application using the Vulert playground without any signup.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

Minimum fixed version

5.17.3-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