CVE-2021-47416
published 2024-05-21CVE-2021-47416: 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…
PriorityP417medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.23%
14.4th percentile
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
22 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.14.12-1 (bookworm) | linux 5.14.12-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 46abc02175b3c246dd5141d878f565a8725060c9 < 25e9f88c7e3cc35f5e3d3db199660d28a15df639 | 25e9f88c7e3cc35f5e3d3db199660d28a15df639 |
| linux | linux | >= 46abc02175b3c246dd5141d878f565a8725060c9 < 2250392d930bd0d989f24d355d6355b0150256e7 | 2250392d930bd0d989f24d355d6355b0150256e7 |
| linux | linux | >= 46abc02175b3c246dd5141d878f565a8725060c9 < f4f502a04ee1e543825af78f47eb7785015cd9f6 | f4f502a04ee1e543825af78f47eb7785015cd9f6 |
| linux | linux | >= 46abc02175b3c246dd5141d878f565a8725060c9 < 2397b9e118721292429fea8807a698e71b94795f | 2397b9e118721292429fea8807a698e71b94795f |
| linux | linux | >= 46abc02175b3c246dd5141d878f565a8725060c9 < 414bb4ead1362ef2c8592db723c017258f213988 | 414bb4ead1362ef2c8592db723c017258f213988 |
| linux | linux | >= 46abc02175b3c246dd5141d878f565a8725060c9 < 0d2dd40a7be61b89a7c99dae8ee96389d27b413a | 0d2dd40a7be61b89a7c99dae8ee96389d27b413a |
| linux | linux | >= 46abc02175b3c246dd5141d878f565a8725060c9 < 064c2616234a7394867c924b5c1303974f3a4f4d | 064c2616234a7394867c924b5c1303974f3a4f4d |
| linux | linux | >= 46abc02175b3c246dd5141d878f565a8725060c9 < ca6e11c337daf7925ff8a2aac8e84490a8691905 | ca6e11c337daf7925ff8a2aac8e84490a8691905 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.84-1 | 5.10.84-1 |
| linux | linux_kernel | >= 0 < 5.14.12-1 | 5.14.12-1 |
| linux | linux_kernel | >= 0 < 5.14.12-1 | 5.14.12-1 |
| linux | linux_kernel | >= 0 < 5.14.12-1 | 5.14.12-1 |
| linux | linux_kernel | >= 2.6.28 < 4.4.289 | 4.4.289 |
| linux | linux_kernel | >= 4.10 < 4.14.251 | 4.14.251 |
| linux | linux_kernel | >= 4.15 < 4.19.211 | 4.19.211 |
| linux | linux_kernel | >= 4.20 < 5.4.153 | 5.4.153 |
| linux | linux_kernel | >= 4.5 < 4.9.287 | 4.9.287 |
| linux | linux_kernel | >= 5.11 < 5.14.12 | 5.14.12 |
| linux | linux_kernel | >= 5.5 < 5.10.73 | 5.10.73 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: phy: mdio: fix memory leak
vendor_redhat·2024-05-21·CVSS 5.5
CVE-2021-47416 [MEDIUM] CWE-401 kernel: phy: mdio: fix memory leak
kernel: phy: mdio: fix memory leak
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.
Package: kernel (Red Hat Enterprise Li
Debian
CVE-2021-47416: linux - In the Linux kernel, the following vulnerability has been resolved: phy: mdio: ...
vendor_debian·2021·CVSS 5.5
CVE-2021-47416 [MEDIUM] CVE-2021-47416: linux - In the Linux kernel, the following vulnerability has been resolved: phy: mdio: ...
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.
Scope: local
bookworm: resolved (fixed in 5.14.12-1)
bullseye: resolved (fi
GHSA
GHSA-j8cp-h624-v86v: In the Linux kernel, the following vulnerability has been resolved:
phy: mdio: fix memory leak
Syzbot reported memory leak in MDIO bus interface, th
ghsa_unreviewed·2024-05-21
CVE-2021-47416 [MEDIUM] CWE-401 GHSA-j8cp-h624-v86v: In the Linux kernel, the following vulnerability has been resolved:
phy: mdio: fix memory leak
Syzbot reported memory leak in MDIO bus interface, th
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.
OSV
CVE-2021-47416: In the Linux kernel, the following vulnerability has been resolved: phy: mdio: fix memory leak Syzbot reported memory leak in MDIO bus interface, the
osv·2024-05-21·CVSS 5.5
CVE-2021-47416 [MEDIUM] CVE-2021-47416: In the Linux kernel, the following vulnerability has been resolved: phy: mdio: fix memory leak Syzbot reported memory leak in MDIO bus interface, the
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.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/064c2616234a7394867c924b5c1303974f3a4f4dhttps://git.kernel.org/stable/c/0d2dd40a7be61b89a7c99dae8ee96389d27b413ahttps://git.kernel.org/stable/c/2250392d930bd0d989f24d355d6355b0150256e7https://git.kernel.org/stable/c/2397b9e118721292429fea8807a698e71b94795fhttps://git.kernel.org/stable/c/25e9f88c7e3cc35f5e3d3db199660d28a15df639https://git.kernel.org/stable/c/414bb4ead1362ef2c8592db723c017258f213988https://git.kernel.org/stable/c/ca6e11c337daf7925ff8a2aac8e84490a8691905https://git.kernel.org/stable/c/f4f502a04ee1e543825af78f47eb7785015cd9f6https://git.kernel.org/stable/c/064c2616234a7394867c924b5c1303974f3a4f4dhttps://git.kernel.org/stable/c/0d2dd40a7be61b89a7c99dae8ee96389d27b413ahttps://git.kernel.org/stable/c/2250392d930bd0d989f24d355d6355b0150256e7https://git.kernel.org/stable/c/2397b9e118721292429fea8807a698e71b94795fhttps://git.kernel.org/stable/c/25e9f88c7e3cc35f5e3d3db199660d28a15df639https://git.kernel.org/stable/c/414bb4ead1362ef2c8592db723c017258f213988https://git.kernel.org/stable/c/ca6e11c337daf7925ff8a2aac8e84490a8691905https://git.kernel.org/stable/c/f4f502a04ee1e543825af78f47eb7785015cd9f6
2024-05-21
Published