Vulnerability in Kernel package: x86/hyperv: Fix NULL deref in set_hv_tscchange_cb() if Hyper-V setup fails

Kernel Updated 02 Oct 2025

Summary

29/11/2021
N/A
No i
Unrated
Not published

GSD-2021-1002309: x86/hyperv: Fix NULL deref in set_hv_tscchange_cb() if Hyper-V setup fails. Affects Kernel versions >= 93286261de1b46339aa27cd4c639b21778f6cade, < 8823ea27fff6084bbb4bc71d15378fae0220b1d8. 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 package is a critical component of the Linux operating system. It provides the core functionality and interfaces for the system's hardware, software, and processes. The x86/hyperv module within the Kernel package is responsible for handling interactions with the Hyper-V virtualization platform. Hyper-V is a hypervisor developed by Microsoft that allows for the creation and management of virtual machines. This vulnerability specifically affects the set_hv_tscchange_cb() function in the x86/hyperv module. If the Hyper-V setup fails, a NULL dereference occurs, leading to a potential security issue.

Vulnerability Detail

The vulnerability arises from a NULL dereference in the set_hv_tscchange_cb() function of the x86/hyperv module when the Hyper-V setup fails. This can be exploited by an attacker to cause a denial-of-service condition or potentially execute arbitrary code with kernel privileges. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in version v4.16 of the Linux Kernel and has been fixed in version v5.15.5 by commit 8823ea27fff6084bbb4bc71d15378fae0220b1d8.

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.

Conclusion

The vulnerability in the Kernel package's x86/hyperv module can lead to a NULL dereference in the set_hv_tscchange_cb() function if the Hyper-V setup fails. This can result in a denial-of-service condition or potential execution of arbitrary code with kernel privileges. It is crucial to update the Linux Kernel package to version v5.15.5 or later to mitigate this vulnerability. For further support and assistance, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability can range from a denial-of-service condition to potential execution of arbitrary code with kernel privileges.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.

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

It is recommended to update the entire Kernel package to the fixed version. Manually patching the vulnerability without updating the entire package may not provide complete protection and could introduce other issues.

You can find more information about this vulnerability in the official Linux Kernel repository. Additionally, you can reach out to info@devnack.com for further support on vulnerability remediation.

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