Out-of-Bound Array Access in net: tulip: de4x5

Kernel Updated 02 Oct 2025

Summary

19/12/2021
N/A
No i
Unrated
Not published

GSD-2021-1002442: net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of bound. Affects Kernel versions < 77ff166909458646e66450e42909e0adacc99049. 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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The net: tulip: de4x5 package is a network driver in the Linux Kernel. It provides support for certain network interface cards (NICs) based on the DECchip 21140 Ethernet controller. The package includes code for handling the communication between the NIC and the operating system. However, a vulnerability has been discovered in the package that allows for out-of-bound array access.

Vulnerability Detail

The vulnerability in net: tulip: de4x5 arises from a problem with the 'lp->phy[8]' array. This array is accessed without proper bounds checking, which can lead to memory corruption or other unexpected behavior. An attacker could potentially exploit this vulnerability to execute arbitrary code, escalate privileges, or cause a denial-of-service condition. The impact and attack plausibility of this vulnerability have not been proven yet.

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 v5.4.164 or later. This fix is implemented in commit 77ff166909458646e66450e42909e0adacc99049. Updating the kernel will ensure that the array access is properly bounded and prevent potential exploitation of the 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 net: tulip: de4x5 package in the Linux Kernel is vulnerable to an out-of-bound array access issue. To mitigate this vulnerability, it is recommended to update the kernel to version v5.4.164 or later. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

net: tulip: de4x5 is a network driver in the Linux Kernel that supports certain NICs based on the DECchip 21140 Ethernet controller.

The impact of this vulnerability could include memory corruption, arbitrary code execution, privilege escalation, or denial-of-service.

To fix this vulnerability, update the Linux Kernel to version v5.4.164 or later.

No specific workaround has been mentioned for this vulnerability.

For more details about this vulnerability, refer to the provided references link.

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 v5.4.164 or later. This fix is implemented in commit 77ff166909458646e66450e42909e0adacc99049. Updating the kernel will ensure that the array access is properly bounded and prevent potential exploitation of the vulnerability.

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.