Поиск уязвимостей
Количество 20
Количество 20
CVE-2022-48814
In the Linux kernel, the following vulnerability has been resolved: net: dsa: seville: register the mdiobus under devres As explained in commits: 74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres") 5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres") mdiobus_free() will panic when called from devm_mdiobus_free() <- devres_release_all() <- __device_release_driver(), and that mdiobus was not previously unregistered. The Seville VSC9959 switch is a platform device, so the initial set of constraints that I thought would cause this (I2C or SPI buses which call ->remove on ->shutdown) do not apply. But there is one more which applies here. If the DSA master itself is on a bus that calls ->remove from ->shutdown (like dpaa2-eth, which is on the fsl-mc bus), there is a device link between the switch and the DSA master, and device_links_unbind_consumers() will unbind the seville switch driver on shutdown. So the same treatment must be applied to all DSA...
CVE-2022-48814
In the Linux kernel, the following vulnerability has been resolved: net: dsa: seville: register the mdiobus under devres As explained in commits: 74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres") 5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres") mdiobus_free() will panic when called from devm_mdiobus_free() <- devres_release_all() <- __device_release_driver(), and that mdiobus was not previously unregistered. The Seville VSC9959 switch is a platform device, so the initial set of constraints that I thought would cause this (I2C or SPI buses which call ->remove on ->shutdown) do not apply. But there is one more which applies here. If the DSA master itself is on a bus that calls ->remove from ->shutdown (like dpaa2-eth, which is on the fsl-mc bus), there is a device link between the switch and the DSA master, and device_links_unbind_consumers() will unbind the seville switch driver on shutdown. So the same treatment must be applied to all DSA...
CVE-2022-48814
In the Linux kernel, the following vulnerability has been resolved: net: dsa: seville: register the mdiobus under devres As explained in commits: 74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres") 5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres") mdiobus_free() will panic when called from devm_mdiobus_free() <- devres_release_all() <- __device_release_driver(), and that mdiobus was not previously unregistered. The Seville VSC9959 switch is a platform device, so the initial set of constraints that I thought would cause this (I2C or SPI buses which call ->remove on ->shutdown) do not apply. But there is one more which applies here. If the DSA master itself is on a bus that calls ->remove from ->shutdown (like dpaa2-eth, which is on the fsl-mc bus), there is a device link between the switch and the DSA master, and device_links_unbind_consumers() will unbind the seville switch driver on shutdown. So the same treatment must be applied to all
CVE-2022-48814
In the Linux kernel, the following vulnerability has been resolved: n ...
GHSA-px8r-2q8w-48v9
In the Linux kernel, the following vulnerability has been resolved: net: dsa: seville: register the mdiobus under devres As explained in commits: 74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres") 5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres") mdiobus_free() will panic when called from devm_mdiobus_free() <- devres_release_all() <- __device_release_driver(), and that mdiobus was not previously unregistered. The Seville VSC9959 switch is a platform device, so the initial set of constraints that I thought would cause this (I2C or SPI buses which call ->remove on ->shutdown) do not apply. But there is one more which applies here. If the DSA master itself is on a bus that calls ->remove from ->shutdown (like dpaa2-eth, which is on the fsl-mc bus), there is a device link between the switch and the DSA master, and device_links_unbind_consumers() will unbind the seville switch driver on shutdown. So the same treatment must be applied to a...
BDU:2025-01079
Уязвимость компонента net ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20250120-03
Множественные уязвимости kernel-lt
ALT-PU-2022-1451
ALT-PU-2022-1451: package `kernel-image-std-def` update to version 5.15.27-alt1
ALT-PU-2022-1511
ALT-PU-2022-1511: package `kernel-image-rpi-un` update to version 5.15.28-alt1
ALT-PU-2022-1387
ALT-PU-2022-1387: package `kernel-image-un-def` update to version 5.16.11-alt1
ALT-PU-2022-1633
ALT-PU-2022-1633: package `kernel-image-un-def` update to version 5.15.32-alt1
SUSE-SU-2024:2929-1
Security update for the Linux Kernel
ALT-PU-2022-1456
ALT-PU-2022-1456: package `kernel-image-mp` update to version 5.16.12-alt1
SUSE-SU-2024:2947-1
Security update for the Linux Kernel
SUSE-SU-2024:2894-1
Security update for the Linux Kernel
ALT-PU-2022-1540
ALT-PU-2022-1540: package `kernel-image-rpi-un` update to version 5.15.28-alt1
ALT-PU-2022-1746
ALT-PU-2022-1746: package `kernel-image-rpi-def` update to version 5.15.33-alt1
SUSE-SU-2024:2939-1
Security update for the Linux Kernel
ALT-PU-2022-1833
ALT-PU-2022-1833: package `kernel-image-rpi-def` update to version 5.15.36-alt1
ALT-PU-2023-1814
ALT-PU-2023-1814: package `kernel-image-rt` update to version 6.1.28-alt1.rt10
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2022-48814 In the Linux kernel, the following vulnerability has been resolved: net: dsa: seville: register the mdiobus under devres As explained in commits: 74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres") 5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres") mdiobus_free() will panic when called from devm_mdiobus_free() <- devres_release_all() <- __device_release_driver(), and that mdiobus was not previously unregistered. The Seville VSC9959 switch is a platform device, so the initial set of constraints that I thought would cause this (I2C or SPI buses which call ->remove on ->shutdown) do not apply. But there is one more which applies here. If the DSA master itself is on a bus that calls ->remove from ->shutdown (like dpaa2-eth, which is on the fsl-mc bus), there is a device link between the switch and the DSA master, and device_links_unbind_consumers() will unbind the seville switch driver on shutdown. So the same treatment must be applied to all DSA... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2022-48814 In the Linux kernel, the following vulnerability has been resolved: net: dsa: seville: register the mdiobus under devres As explained in commits: 74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres") 5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres") mdiobus_free() will panic when called from devm_mdiobus_free() <- devres_release_all() <- __device_release_driver(), and that mdiobus was not previously unregistered. The Seville VSC9959 switch is a platform device, so the initial set of constraints that I thought would cause this (I2C or SPI buses which call ->remove on ->shutdown) do not apply. But there is one more which applies here. If the DSA master itself is on a bus that calls ->remove from ->shutdown (like dpaa2-eth, which is on the fsl-mc bus), there is a device link between the switch and the DSA master, and device_links_unbind_consumers() will unbind the seville switch driver on shutdown. So the same treatment must be applied to all DSA... | CVSS3: 4.4 | 0% Низкий | больше 2 лет назад | |
CVE-2022-48814 In the Linux kernel, the following vulnerability has been resolved: net: dsa: seville: register the mdiobus under devres As explained in commits: 74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres") 5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres") mdiobus_free() will panic when called from devm_mdiobus_free() <- devres_release_all() <- __device_release_driver(), and that mdiobus was not previously unregistered. The Seville VSC9959 switch is a platform device, so the initial set of constraints that I thought would cause this (I2C or SPI buses which call ->remove on ->shutdown) do not apply. But there is one more which applies here. If the DSA master itself is on a bus that calls ->remove from ->shutdown (like dpaa2-eth, which is on the fsl-mc bus), there is a device link between the switch and the DSA master, and device_links_unbind_consumers() will unbind the seville switch driver on shutdown. So the same treatment must be applied to all | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2022-48814 In the Linux kernel, the following vulnerability has been resolved: n ... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
GHSA-px8r-2q8w-48v9 In the Linux kernel, the following vulnerability has been resolved: net: dsa: seville: register the mdiobus under devres As explained in commits: 74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres") 5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres") mdiobus_free() will panic when called from devm_mdiobus_free() <- devres_release_all() <- __device_release_driver(), and that mdiobus was not previously unregistered. The Seville VSC9959 switch is a platform device, so the initial set of constraints that I thought would cause this (I2C or SPI buses which call ->remove on ->shutdown) do not apply. But there is one more which applies here. If the DSA master itself is on a bus that calls ->remove from ->shutdown (like dpaa2-eth, which is on the fsl-mc bus), there is a device link between the switch and the DSA master, and device_links_unbind_consumers() will unbind the seville switch driver on shutdown. So the same treatment must be applied to a... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
BDU:2025-01079 Уязвимость компонента net ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 4.4 | 0% Низкий | почти 5 лет назад | |
ROS-20250120-03 Множественные уязвимости kernel-lt | CVSS3: 5.5 | почти 2 года назад | ||
ALT-PU-2022-1451 ALT-PU-2022-1451: package `kernel-image-std-def` update to version 5.15.27-alt1 | CVSS3: 7.8 | больше 4 лет назад | ||
ALT-PU-2022-1511 ALT-PU-2022-1511: package `kernel-image-rpi-un` update to version 5.15.28-alt1 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-1387 ALT-PU-2022-1387: package `kernel-image-un-def` update to version 5.16.11-alt1 | CVSS3: 8.4 | больше 4 лет назад | ||
ALT-PU-2022-1633 ALT-PU-2022-1633: package `kernel-image-un-def` update to version 5.15.32-alt1 | CVSS3: 8.8 | больше 4 лет назад | ||
SUSE-SU-2024:2929-1 Security update for the Linux Kernel | около 2 лет назад | |||
ALT-PU-2022-1456 ALT-PU-2022-1456: package `kernel-image-mp` update to version 5.16.12-alt1 | CVSS3: 8.8 | больше 4 лет назад | ||
SUSE-SU-2024:2947-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:2894-1 Security update for the Linux Kernel | около 2 лет назад | |||
ALT-PU-2022-1540 ALT-PU-2022-1540: package `kernel-image-rpi-un` update to version 5.15.28-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-1746 ALT-PU-2022-1746: package `kernel-image-rpi-def` update to version 5.15.33-alt1 | CVSS3: 8.8 | больше 4 лет назад | ||
SUSE-SU-2024:2939-1 Security update for the Linux Kernel | около 2 лет назад | |||
ALT-PU-2022-1833 ALT-PU-2022-1833: package `kernel-image-rpi-def` update to version 5.15.36-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2023-1814 ALT-PU-2023-1814: package `kernel-image-rt` update to version 6.1.28-alt1.rt10 | CVSS3: 9.8 | больше 3 лет назад |
Уязвимостей на страницу