Out-of-Bound Array Access in net: tulip: de4x5
Summary
GSD-2021-1002358: net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of bound. Affects Kernel versions < ec5bd0aef1cec96830d0c7e06d3597d9e786cc98. 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 net: tulip: de4x5 package is a component of the Linux Kernel, which is responsible for managing network interfaces. It includes support for the DECchip 21040, 21041, and 21140 Ethernet controllers. These controllers are commonly used in various network devices. However, a vulnerability has been identified in the package that allows for out-of-bound array access.
Vulnerability Detail
The vulnerability in net: tulip: de4x5 arises from the potential out-of-bound access to the 'lp->phy[8]' array. This array is used to store physical layer information for the network interface. By accessing an element beyond the array bounds, an attacker could potentially overwrite adjacent memory or cause a crash in the system. The impact and attack plausibility of this vulnerability 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 specific workaround mentioned for this vulnerability.
Conclusion
The out-of-bound array access vulnerability in net: tulip: de4x5 can be mitigated by updating the Linux Kernel to version v4.4.294 or later. This fix ensures that the array access is within bounds, reducing the risk of memory corruption or system crashes. For further support on vulnerability remediation, contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
net: tulip: de4x5 is a component of the Linux Kernel that provides support for DECchip Ethernet controllers.
The impact of this vulnerability is not yet proven, but it could potentially lead to memory corruption or system crashes.
To fix this vulnerability, update the Linux Kernel to version v4.4.294 or later.
No specific workaround has been mentioned for this vulnerability.
For more details, refer to the vulnerability report at the provided source link.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
