Количество 23
Количество 23
BDU:2025-14223
Уязвимость функции __mdiobus_register() модуля drivers/net/phy/mdio_bus.c драйвера поддержки сетевых адаптеров ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
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 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.
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 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.
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 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.
CVE-2021-47416
In the Linux kernel, the following vulnerability has been resolved: p ...
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, 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.
SUSE-SU-2024:4103-1
Security update for the Linux Kernel
SUSE-SU-2024:4140-1
Security update for the Linux Kernel
SUSE-SU-2024:4131-1
Security update for the Linux Kernel
SUSE-SU-2025:0034-1
Security update for the Linux Kernel
SUSE-SU-2024:4100-1
Security update for the Linux Kernel
SUSE-SU-2024:2183-1
Security update for the Linux Kernel
SUSE-SU-2024:1979-1
Security update for the Linux Kernel
SUSE-SU-2024:2185-1
Security update for the Linux Kernel
SUSE-SU-2024:2184-1
Security update for the Linux Kernel
SUSE-SU-2024:1983-1
Security update for the Linux Kernel
SUSE-SU-2024:3983-1
Security update for the Linux Kernel
SUSE-SU-2024:3985-1
Security update for the Linux Kernel
SUSE-SU-2024:2189-1
Security update for the Linux Kernel
SUSE-SU-2024:4364-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | BDU:2025-14223 Уязвимость функции __mdiobus_register() модуля drivers/net/phy/mdio_bus.c драйвера поддержки сетевых адаптеров ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | почти 5 лет назад |
 | 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 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. | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад |
 | 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 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. | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад |
 | 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 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. | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад |
| CVE-2021-47416 In the Linux kernel, the following vulnerability has been resolved: p ... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад |
| 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, 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. | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад |
 | SUSE-SU-2024:4103-1 Security update for the Linux Kernel | больше 1 года назад | ||
| SUSE-SU-2024:4140-1 Security update for the Linux Kernel | больше 1 года назад | ||
| SUSE-SU-2024:4131-1 Security update for the Linux Kernel | больше 1 года назад | ||
| SUSE-SU-2025:0034-1 Security update for the Linux Kernel | больше 1 года назад | ||
| SUSE-SU-2024:4100-1 Security update for the Linux Kernel | больше 1 года назад | ||
| SUSE-SU-2024:2183-1 Security update for the Linux Kernel | около 2 лет назад | ||
| SUSE-SU-2024:1979-1 Security update for the Linux Kernel | около 2 лет назад | ||
| SUSE-SU-2024:2185-1 Security update for the Linux Kernel | около 2 лет назад | ||
| SUSE-SU-2024:2184-1 Security update for the Linux Kernel | около 2 лет назад | ||
| SUSE-SU-2024:1983-1 Security update for the Linux Kernel | около 2 лет назад | ||
| SUSE-SU-2024:3983-1 Security update for the Linux Kernel | почти 2 года назад | ||
| SUSE-SU-2024:3985-1 Security update for the Linux Kernel | почти 2 года назад | ||
| SUSE-SU-2024:2189-1 Security update for the Linux Kernel | около 2 лет назад | ||
| SUSE-SU-2024:4364-1 Security update for the Linux Kernel | больше 1 года назад |
Уязвимостей на страницу