Memory Corruption Vulnerability in vduse_dev_ioctl() in Linux Kernel

Kernel Updated 02 Oct 2025

Summary

27/12/2021
N/A
No i
Unrated
Not published

GSD-2021-1002732: vduse: fix memory corruption in vduse_dev_ioctl(). Affects Kernel versions >= c8a6153b6c59d95c0e091f053f6f180952ade91e, < e6c67560b4341914bec32ec536e931c22062af65. 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 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 the Linux operating system, responsible for managing system resources and providing an interface for applications to interact with the hardware. The vduse_dev_ioctl() function is part of the vduse driver, which is used for virtual device communication in the Linux Kernel. This vulnerability affects the Linux Kernel versions 5.15 to 5.15.10 and can lead to memory corruption.

Vulnerability Detail

The vduse_dev_ioctl() function in the Linux Kernel is vulnerable to memory corruption. This vulnerability was introduced in version 5.15 of the Linux Kernel and was fixed in version 5.15.11. An attacker could exploit this vulnerability to corrupt memory, potentially leading to arbitrary code execution or system crashes. The exact impact and attack vectors have not been proven yet.

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 known workaround for this vulnerability at the moment.

Conclusion

In conclusion, a memory corruption vulnerability has been discovered in the vduse_dev_ioctl() function in the Linux Kernel. This vulnerability can potentially lead to arbitrary code execution or system crashes. It is crucial to update the Linux Kernel to version 5.15.11 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability could potentially allow an attacker to corrupt memory, leading to arbitrary code execution or system crashes.

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 analyze and alert you in real-time.

There is no known exploit for this vulnerability at the moment. However, it is important to apply the fix as soon as possible to mitigate any potential risks.

The specific prerequisites for exploiting this vulnerability have not been determined yet. It is recommended to apply the fix as a precautionary measure.

The remote exploitability of this vulnerability has not been determined yet. However, it is always recommended to keep systems up to date with the latest security patches to minimize the risk of remote exploitation.

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