Vulnerability · Published May 21, 2024 · Assigned by Linux

CVE-2021-47416phy: mdio: fix memory leak

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 14% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 85.7% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: phy: mdio: fix memory leak Syzbot reported memory leak in MDIO bus interface, the problem was in wrong state logic. MDIOBUS_ALLOCATED indicates 2 states: 1. Bus is only allocated 2. Bus allocated and __mdiobus_register() fails, but device_register() was called In case of device_register() has been called we should call put_device() to correctly free the memory allocated for this device, but mdiobus_free() calls just kfree(dev) in case of MDIOBUS_ALLOCATED state To avoid this behaviour we need to set bus->state to MDIOBUS_UNREGISTERED _before_ calling device_register(), because put_device() should be called even in case of device_register() failure.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux5.14.12-1DEBIAN-CVE-2021-47416
Debian:13linux5.14.12-1DEBIAN-CVE-2021-47416
Debian:14linux5.14.12-1DEBIAN-CVE-2021-47416
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2021-47416
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2021-47416
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2021-47416

Affected products (as reported)

VendorProductVersions
Linux Linux 46abc02175b3c246dd5141d878f565a8725060c9 – before 25e9f88c7e3cc35f5e3d3db199660d28a15df63946abc02175b3c246dd5141d878f565a8725060c9 – before 2250392d930bd0d989f24d355d6355b0150256e746abc02175b3c246dd5141d878f565a8725060c9 – before f4f502a04ee1e543825af78f47eb7785015cd9f646abc02175b3c246dd5141d878f565a8725060c9 – before 2397b9e118721292429fea8807a698e71b94795f46abc02175b3c246dd5141d878f565a8725060c9 – before 414bb4ead1362ef2c8592db723c017258f21398846abc02175b3c246dd5141d878f565a8725060c9 – before 0d2dd40a7be61b89a7c99dae8ee96389d27b413a46abc02175b3c246dd5141d878f565a8725060c9 – before 064c2616234a7394867c924b5c1303974f3a4f4d46abc02175b3c246dd5141d878f565a8725060c9 – before ca6e11c337daf7925ff8a2aac8e84490a8691905
Linux Linux 2.6.28

References