Skip to content
Fencer Intel
medium 4.4

CVE-2021-47547 json

net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of bound

published 2y ago modified 4mo ago also EUVD-2021-34549

cvss
4.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 4.4.294, 4.9.292, 4.14.257, 4.19.220, 5.4.164, 5.10.84, 5.15.7, 5.16
  • linux Debian 14, Debian 13, Debian 12 5.15.15-1

debian advisories DEBIAN-CVE-2021-47547

  • linux Ubuntu 18.04 LTS 4.15.0-169.177
  • linux Ubuntu 20.04 LTS 5.4.0-100.113
  • linux-aws Ubuntu 18.04 LTS 4.15.0-1121.129
  • linux-aws Ubuntu 20.04 LTS 5.4.0-1066.69
  • linux-gcp Ubuntu 20.04 LTS 5.4.0-1065.69
  • linux-ibm Ubuntu 20.04 LTS 5.4.0-1015.16
  • linux-kvm Ubuntu 18.04 LTS 4.15.0-1107.109
  • linux-kvm Ubuntu 20.04 LTS 5.4.0-1056.58

ubuntu advisories UBUNTU-CVE-2021-47547

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-azure SLE Module for Public Cloud 15 SP5, openSUSE Leap 15.5 5.14.21-150500.33.63.1
  • kernel-syms-azure SLE Module for Public Cloud 15 SP5, openSUSE Leap 15.5 5.14.21-150500.33.63.1
  • kernel-source-azure SLE Module for Public Cloud 15 SP5, openSUSE Leap 15.5 5.14.21-150500.33.63.1
  • dtb-aarch64 openSUSE Leap 15.5 5.14.21-150500.55.73.1
  • kernel-64kb SLE Module for Basesystem 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.73.1
  • kernel-syms SLE Module for Development Tools 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.73.1
  • kernel-obs-qa openSUSE Leap 15.5 5.14.21-150500.55.73.1
  • kernel-source SLE Module for Development Tools 15 SP5, SLE Module for Basesystem 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.73.1

suse advisories SUSE-SU-2024:2947-1SUSE-SU-2024:2939-1SUSE-SU-2024:2901-1SUSE-SU-2024:2894-1SUSE-SU-2024:2561-1SUSE-SU-2024:2493-1

Is CVE-2021-47547 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-47547 updated cvss 6.1

kernel: net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of bound

  • Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 4.4 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
CNA 3.1 4.4 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Affected products

  • Linux Linux

Classification

Weakness
  • CWE-129 Improper Validation of Array Index
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.