Double Free Vulnerability in rpmsg: virtio Package
Summary
GSD-2022-1002642: rpmsg: virtio: Fix possible double free in rpmsg_virtio_add_ctrl_dev(). Affects Kernel versions >= c486682ae1e2b149add22f44cf413b3103e3ef39, < d51720ac069d465101d937273acecde1f71ea411. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The rpmsg: virtio package is a component of the Linux Kernel that provides support for remote processor messaging. It allows communication between different processors in a system through a virtio transport. The package is responsible for managing control devices and ensuring secure and reliable communication. However, a vulnerability has been discovered in the package that could lead to a double free issue.
Vulnerability Detail
The vulnerability, identified as GSD-2022-1002642, exists in the rpmsg_virtio_add_ctrl_dev() function of the rpmsg: virtio package. It is caused by improper handling of control devices, which can result in a double free scenario. An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition. The vulnerability was introduced in version v5.13 of the Linux Kernel and has been fixed in version v5.18.4.
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. It is essential to apply the provided fix by updating the Linux Kernel to the recommended version.
Conclusion
The double free vulnerability in the rpmsg: virtio package can have severe consequences, including arbitrary code execution and denial-of-service attacks. It is crucial to update the Linux Kernel to version v5.18.4 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability could allow an attacker to execute arbitrary code or cause a denial-of-service condition.
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 alerts for open-source vulnerabilities.
No, there is no known workaround for this vulnerability. Updating the Linux Kernel to the recommended version is the only solution.
There are no known exploits for this vulnerability at the moment. However, it is crucial to apply the fix promptly to mitigate any potential risks.
You can find more information about this vulnerability in the GSD-2022-1002642 JSON report available at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1002xxx/GSD-2022-1002642.json.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
