Vulnerability in Kernel Package: drm/i915/gvt

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1001726: drm/i915/gvt: fix the usage of ww lock in gvt scheduler. Affects Kernel versions >= 67f1120381df022a7016f4acc8d4880da9a66c03, < ce1cccb000bda07a172518894c3439c1cb699f42. 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 fundamental component of the Linux operating system, responsible for managing the system's core functionality. It includes various subsystems, such as the Direct Rendering Manager (drm), which handles graphics rendering. The drm/i915/gvt subsystem specifically focuses on virtualization support for Intel graphics hardware. This vulnerability affects the gvt scheduler within the drm/i915/gvt subsystem.

Vulnerability Detail

The vulnerability in the gvt scheduler of the drm/i915/gvt subsystem involves incorrect usage of a ww lock. This issue was introduced in version v5.12 of the Linux Kernel and fixed in version v5.14.10. The impact and attack plausibility of this vulnerability have not been proven yet. However, if exploited, it could potentially lead to security breaches or system instability. The specific technical details of the vulnerability can be found in the references link.

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 commit ce1cccb000bda07a172518894c3439c1cb699f42, which addresses the issue. Updating the Kernel ensures that the incorrect usage of the ww lock in the gvt scheduler is resolved.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Conclusion

In conclusion, the vulnerability in the drm/i915/gvt subsystem of the Kernel package involves incorrect usage of a ww lock. While the impact and attack plausibility have not been proven, it is recommended to update the Linux Kernel to version v5.14.10 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability is not yet proven. However, if exploited, it could potentially lead to security breaches or system instability.

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 provide real-time monitoring and alerts for open-source vulnerabilities.

No specific workaround has been mentioned for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.

You can find more information about this vulnerability in the references link provided.

To update the Linux Kernel, you can follow the official documentation or guidelines provided by your Linux distribution. Typically, it involves using package managers or downloading the latest Kernel version from the official Linux Kernel website.

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 commit ce1cccb000bda07a172518894c3439c1cb699f42, which addresses the issue. Updating the Kernel ensures that the incorrect usage of the ww lock in the gvt scheduler is resolved.

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.