Vulnerability in vhost/vsock Package: Owner Check Bypass in vhost_vsock_stop()

Kernel Updated 02 Oct 2025

Summary

18/03/2022
N/A
No i
Unrated
Not published

GSD-2022-1000868: vhost/vsock: don't check owner in vhost_vsock_stop() while releasing. Affects Kernel versions >= 433fc58e6bf2c8bd97e57153ed28e64fd78207b8, < 698dc7d13c4e972214458996455447651a657264. 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 vhost/vsock package is a component of the Linux Kernel, which provides support for virtual sockets (vsock) in the virtual host (vhost) environment. This package allows communication between the host and guest operating systems in virtualized environments. The vhost/vsock package is responsible for managing the lifecycle of vsock devices and ensuring secure communication between the host and guest systems.

Vulnerability Detail

The vulnerability in the vhost/vsock package resides in the vhost_vsock_stop() function. In this function, the owner of the vsock device is not properly checked before releasing the resources associated with it. This oversight allows an attacker with access to a vsock device to bypass the owner check during the release process. By exploiting this vulnerability, an attacker could potentially gain unauthorized access to the vsock device and perform malicious actions, such as intercepting or modifying communication between the host and guest systems.

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

As a temporary workaround, users can restrict access to the vhost/vsock package by implementing appropriate access controls and permissions. This can help mitigate the risk of unauthorized access to vsock devices. However, applying the official patch or updating the Linux Kernel is the recommended long-term solution.

Conclusion

The vulnerability in the vhost/vsock package allows for the bypass of the owner check during the release of vsock devices. This could lead to unauthorized access and potential compromise of communication between the host and guest systems in virtualized environments. It is crucial to update the Linux Kernel to version v5.10.103 or later to mitigate this vulnerability. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability allows an attacker to bypass the owner check in the vhost/vsock package, potentially leading to unauthorized access to vsock devices and compromising the communication between the host and guest systems in virtualized environments.

You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert analyzes package-lock.json files to identify and alert for open-source vulnerabilities in real-time.

At the time of this report, there is no known public exploit for this vulnerability. However, it is important to apply the recommended fixes and updates to mitigate the risk of potential exploitation.

To exploit this vulnerability, an attacker would require access to a vsock device in a virtualized environment. Additionally, the attacker would need to bypass any access controls or permissions implemented by the system administrator.

This vulnerability was discovered by the Linux Kernel security team during routine code review and analysis.

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