CVE-2021-47547: net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of bound
In the Linux kernel, the following vulnerability has been resolved:
net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of bound
In line 5001, if all id in the array 'lp->phy[8]' is not 0, when the
'for' end, the 'k' is 8.
At this time, the array 'lp->phy[8]' may be out of bound.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47547 is a Linux kernel bug in the tulip de4x5 network driver. A local, low-privileged user could potentially cause limited integrity or availability impact. The public record rates it medium with CVSS 4.4. No provided source says it is being actively exploited.
Executive priority
Treat as routine but real kernel maintenance. It is not internet-exploitable from the supplied evidence, but local kernel bugs can matter on shared systems, developer workstations, and servers where untrusted users or workloads run.
Technical view
The issue is an out-of-bounds access risk involving the lp->phy[8] array in the Linux kernel de4x5 driver. If all IDs in the array are nonzero, loop index k can reach 8 and access beyond the array boundary. The Linux stable commits are listed as the resolution.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions where the tulip de4x5 driver is present or relevant. The bundle lists Linux as the affected product and includes multiple stable branch fix commits, but does not identify specific distributions or appliances.
Exploitation context
The CVSS vector is local, low complexity, low privilege, no user interaction, with limited integrity and availability impact. CISA KEV status is false, and the supplied sources do not report public exploitation or exploit availability.
Researcher notes
The core condition is k reaching 8 after scanning lp->phy[8], creating an out-of-bounds reference. The source bundle does not provide proof-of-concept details, affected distribution mappings, or named mitigations beyond the stable kernel fixes.
Mitigation direction
Apply Linux kernel updates containing the referenced stable fixes.
Check your Linux distribution advisories for backported fixes.
Prioritize systems where the de4x5 driver is present or used.
If patching is delayed, request supported workaround guidance from the vendor.
Validation and detection
Inventory Linux kernel versions across managed hosts.
Check whether the tulip de4x5 driver exists or is loaded.
Confirm vendor kernel packages include the referenced stable fix commits.
Track remediation through normal kernel update and reboot processes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-47547 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.