Double Free Vulnerability in rpmsg: virtio

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1003291: rpmsg: virtio: Fix possible double free in rpmsg_virtio_add_ctrl_dev(). Affects Kernel versions >= c486682ae1e2b149add22f44cf413b3103e3ef39, < b94d40c792de7f0ceda6a2fd8a8dc0597eca6d22. 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 rpmsg: virtio package is a component of the Linux Kernel that provides support for the Remote Processor Messaging (RPMsg) protocol over the VirtIO transport. RPMsg is a lightweight interprocessor communication framework used in embedded systems. The virtio driver allows communication between the host and guest operating systems in a virtualized environment. This vulnerability affects versions 5.13 to 5.15.46 of the Linux Kernel.

Vulnerability Detail

The rpmsg_virtio_add_ctrl_dev() function in the rpmsg: virtio package is susceptible to a double free vulnerability. This vulnerability was introduced in version 5.13 of the Linux Kernel and fixed in version 5.15.47. An attacker could exploit this vulnerability to cause a denial-of-service (DoS) condition or potentially execute arbitrary code. The vulnerability occurs when the function attempts to add a control device and encounters an error, leading to a double free of the device structure.

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 5.15.47 or later. This fix can be obtained by pulling the latest updates from the official Linux Kernel repository. Alternatively, users can apply the specific commit (b94d40c792de7f0ceda6a2fd8a8dc0597eca6d22) that addresses this issue.

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

Workaround

No workaround has been provided for this vulnerability.

Conclusion

The double free vulnerability in rpmsg: virtio can potentially lead to a denial-of-service (DoS) condition or arbitrary code execution. It is crucial to update the Linux Kernel to version 5.15.47 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 lead to a denial-of-service (DoS) condition or allow an attacker to execute arbitrary code.

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

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

The only known mitigation for this vulnerability is to update the Linux Kernel to version 5.15.47 or later.

You can find more information about this vulnerability in the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/).

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 5.15.47 or later. This fix can be obtained by pulling the latest updates from the official Linux Kernel repository. Alternatively, users can apply the specific commit (b94d40c792de7f0ceda6a2fd8a8dc0597eca6d22) that addresses this issue.

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.