7 matches found
Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989731)
The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-989731 advisory. In the Linux kernel, the following vulnerability has been resolved: net: tulip: de4x5: fix the problem that the array 'lp-phy8' may be out of bound In line 5001, if...
Linux Distros Unpatched Vulnerability : CVE-2021-47547
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - net: tulip: de4x5: fix the problem that the array 'lp-phy8' may be out of bound In line 5001, if all id in the array 'lp-phy8' is not 0, when the 'for' end, the...
DEBIAN-CVE-2021-47547
In the Linux kernel, the following vulnerability has been resolved: net: tulip: de4x5: fix the problem that the array 'lp-phy8' may be out of bound In line 5001, if all id in the array 'lp-phy8' is not 0, when the 'for' end, the 'k' is 8. At this time, the array 'lp-phy8' may be out of bound...
SUSE CVE-2020-11102
hw/net/tulip.c in QEMU 4.2.0 has a buffer overflow during the copying of tx/rx buffers because the frame size is not validated against the r/w data length...
The vulnerability in the `hw/net/tulip.c` component of the QEMU hardware emulation software involves writing beyond the buffer boundaries. This allows an attacker to access confidential data, compromise its integrity, and cause service failures.
The vulnerability in the hw/net/tulip.c component of the QEMU hardware emulation software involves writing beyond the buffer boundaries during copy operations for TX/RX data. Exploiting this vulnerability can allow a remote attacker to gain access to confidential data, compromise its integrity, a...
hw/net/tulip.c in QEMU 4.2.0 has a buffer overflow during the copying of tx/rx buffers because the frame size is not validated against the r/w data length.
...
DEBIAN-CVE-2020-11102
hw/net/tulip.c in QEMU 4.2.0 has a buffer overflow during the copying of tx/rx buffers because the frame size is not validated against the r/w data length...