Vulnerability in sr9700: Sanity Check for Packet Length
Summary
GSD-2022-1000866: sr9700: sanity check for packet length. Affects Kernel versions < 4f5f5411f0c14ac0b61d5e6a77d996dd3d5b5fd3. 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 sr9700 package is a driver for the USB to Ethernet converter chip manufactured by SMC. It provides support for connecting devices with USB interfaces to Ethernet networks. The vulnerability in this package relates to a missing sanity check for packet length. This oversight could potentially allow an attacker to send specially crafted packets that exceed the expected length, leading to buffer overflows or other memory corruption issues.
Vulnerability Detail
The vulnerability in the sr9700 package arises from the absence of a proper sanity check for packet length. Without this check, an attacker can send packets that are longer than expected, potentially causing buffer overflows or other memory corruption issues. The impact of this vulnerability is dependent on the specific usage scenario and the attacker's capabilities. If successfully exploited, it could lead to remote code execution, denial of service, or other security breaches. The vulnerability has been addressed in the Linux Kernel version v5.10.103 by commit 4f5f5411f0c14ac0b61d5e6a77d996dd3d5b5fd3.
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 →
Conclusion
In conclusion, the sr9700 package is vulnerable to a missing sanity check for packet length. This vulnerability can potentially lead to buffer overflows or other memory corruption issues if exploited. To mitigate this vulnerability, it is crucial to update the affected package to the latest version of the Linux Kernel (v5.10.103 or later). For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can vary depending on the specific usage scenario and the attacker's capabilities. If successfully exploited, it could lead to remote code execution, denial of service, or other security breaches.
Yes, this vulnerability has been fixed in the Linux Kernel version v5.10.103 by commit 4f5f5411f0c14ac0b61d5e6a77d996dd3d5b5fd3.
To protect your system, it is recommended to update the affected package to the latest version of the Linux Kernel (v5.10.103 or later). This update includes the necessary fix for the vulnerability.
No, there are no known workarounds for this vulnerability. It is recommended to apply the provided fix by updating the affected package.
You can find more information about this vulnerability in the Open Source Vulnerability Database (OSVDB) entry with ID GSD-2022-1000866.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
