memcpy() overflow vulnerability in Kernel: qed
Summary
UVI-2021-1001120: net: qed: Fix memcpy() overflow of qed_dcbx_params(). Affects Kernel versions < 70866199220ebae6161728944a76ad071ff908d1. 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 Kernel is a crucial component of the Linux operating system, responsible for managing system resources and facilitating communication between hardware and software. The qed module within the Kernel is specifically designed for QLogic Ethernet devices. It provides support for various features, including Data Center Bridging Exchange (DCBX) parameters. These parameters are used to negotiate and configure network settings in data center environments. However, a vulnerability has been discovered in the qed_dcbx_params() function, which can lead to a memcpy() overflow.
Vulnerability Detail
The vulnerability in the qed_dcbx_params() function arises from an unchecked memcpy() operation. An attacker could exploit this vulnerability by providing malicious input, causing the memcpy() operation to overflow its destination buffer. This could result in arbitrary code execution or a denial-of-service condition. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability has been addressed in the Linux Kernel version v5.4.129 by commit 70866199220ebae6161728944a76ad071ff908d1.
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
No specific workaround has been mentioned for this vulnerability.
Conclusion
The memcpy() overflow vulnerability in the Kernel's qed module poses a potential risk of arbitrary code execution or denial-of-service. It is crucial to update the Linux Kernel to version v5.4.129 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could potentially lead to arbitrary code execution or a denial-of-service condition. However, the actual impact and attack plausibility have not been proven yet.
You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and Vulert will analyze it for open-source vulnerabilities in real-time.
Yes, the vulnerability has been fixed in the Linux Kernel version v5.4.129 by commit 70866199220ebae6161728944a76ad071ff908d1. Users should update their Kernel to this version or later to mitigate the vulnerability.
While no specific temporary measures have been mentioned for this vulnerability, it is generally recommended to follow security best practices such as keeping software and systems up to date, implementing proper access controls, and monitoring for any suspicious activity.
You can refer to the vulnerability details in the Cloud Security Alliance's GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1001xxx/UVI-2021-1001120.json) for more information about this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
