Поиск уязвимостей
Количество 18
Количество 18
CVE-2022-50260
In the Linux kernel, the following vulnerability has been resolved: drm/msm: Make .remove and .shutdown HW shutdown consistent Drivers' .remove and .shutdown callbacks are executed on different code paths. The former is called when a device is removed from the bus, while the latter is called at system shutdown time to quiesce the device. This means that some overlap exists between the two, because both have to take care of properly shutting down the hardware. But currently the logic used in these two callbacks isn't consistent in msm drivers, which could lead to kernel panic. For example, on .remove the component is deleted and its .unbind callback leads to the hardware being shutdown but only if the DRM device has been marked as registered. That check doesn't exist in the .shutdown logic and this can lead to the driver calling drm_atomic_helper_shutdown() for a DRM device that hasn't been properly initialized. A situation like this can happen if drivers for expected sub-devices fai...
CVE-2022-50260
In the Linux kernel, the following vulnerability has been resolved: drm/msm: Make .remove and .shutdown HW shutdown consistent Drivers' .remove and .shutdown callbacks are executed on different code paths. The former is called when a device is removed from the bus, while the latter is called at system shutdown time to quiesce the device. This means that some overlap exists between the two, because both have to take care of properly shutting down the hardware. But currently the logic used in these two callbacks isn't consistent in msm drivers, which could lead to kernel panic. For example, on .remove the component is deleted and its .unbind callback leads to the hardware being shutdown but only if the DRM device has been marked as registered. That check doesn't exist in the .shutdown logic and this can lead to the driver calling drm_atomic_helper_shutdown() for a DRM device that hasn't been properly initialized. A situation like this can happen if drivers for expected sub-devices fai...
CVE-2022-50260
In the Linux kernel, the following vulnerability has been resolved: drm/msm: Make .remove and .shutdown HW shutdown consistent Drivers' .remove and .shutdown callbacks are executed on different code paths. The former is called when a device is removed from the bus, while the latter is called at system shutdown time to quiesce the device. This means that some overlap exists between the two, because both have to take care of properly shutting down the hardware. But currently the logic used in these two callbacks isn't consistent in msm drivers, which could lead to kernel panic. For example, on .remove the component is deleted and its .unbind callback leads to the hardware being shutdown but only if the DRM device has been marked as registered. That check doesn't exist in the .shutdown logic and this can lead to the driver calling drm_atomic_helper_shutdown() for a DRM device that hasn't been properly initialized. A situation like this can happen if drivers for expected sub-devices
CVE-2022-50260
drm/msm: Make .remove and .shutdown HW shutdown consistent
CVE-2022-50260
In the Linux kernel, the following vulnerability has been resolved: d ...
GHSA-wv25-jjx7-r2r4
In the Linux kernel, the following vulnerability has been resolved: drm/msm: Make .remove and .shutdown HW shutdown consistent Drivers' .remove and .shutdown callbacks are executed on different code paths. The former is called when a device is removed from the bus, while the latter is called at system shutdown time to quiesce the device. This means that some overlap exists between the two, because both have to take care of properly shutting down the hardware. But currently the logic used in these two callbacks isn't consistent in msm drivers, which could lead to kernel panic. For example, on .remove the component is deleted and its .unbind callback leads to the hardware being shutdown but only if the DRM device has been marked as registered. That check doesn't exist in the .shutdown logic and this can lead to the driver calling drm_atomic_helper_shutdown() for a DRM device that hasn't been properly initialized. A situation like this can happen if drivers for expected sub-devic...
BDU:2026-08817
Уязвимость функции msm_drv_shutdown() модуля drivers/gpu/drm/msm/msm_drv.c драйвера инфраструктуры прямого рендеринга (DRI) ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ALT-PU-2020-3058
ALT-PU-2020-3058: package `kernel-image-un-def` update to version 5.9.0-alt1
SUSE-SU-2025:03626-1
Security update for the Linux Kernel
ALT-PU-2022-2913
ALT-PU-2022-2913: package `kernel-image-un-def` update to version 5.19.17-alt1
ALT-PU-2022-2925
ALT-PU-2022-2925: package `kernel-image-mp` update to version 6.0.4-alt1
SUSE-SU-2025:03628-1
Security update for the Linux Kernel
SUSE-SU-2025:03615-1
Security update for the Linux Kernel
ALT-PU-2023-1741
ALT-PU-2023-1741: package `kernel-image-un-def` update to version 6.1.26-alt1
ALT-PU-2023-1684
ALT-PU-2023-1684: package `kernel-image-std-def` update to version 6.1.26-alt1
ALT-PU-2022-3371
ALT-PU-2022-3371: package `kernel-image-rpi-un` update to version 6.1.0-alt1
ALT-PU-2022-3364
ALT-PU-2022-3364: package `kernel-image-rpi-un` update to version 6.1.0-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-50260 In the Linux kernel, the following vulnerability has been resolved: drm/msm: Make .remove and .shutdown HW shutdown consistent Drivers' .remove and .shutdown callbacks are executed on different code paths. The former is called when a device is removed from the bus, while the latter is called at system shutdown time to quiesce the device. This means that some overlap exists between the two, because both have to take care of properly shutting down the hardware. But currently the logic used in these two callbacks isn't consistent in msm drivers, which could lead to kernel panic. For example, on .remove the component is deleted and its .unbind callback leads to the hardware being shutdown but only if the DRM device has been marked as registered. That check doesn't exist in the .shutdown logic and this can lead to the driver calling drm_atomic_helper_shutdown() for a DRM device that hasn't been properly initialized. A situation like this can happen if drivers for expected sub-devices fai... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2022-50260 In the Linux kernel, the following vulnerability has been resolved: drm/msm: Make .remove and .shutdown HW shutdown consistent Drivers' .remove and .shutdown callbacks are executed on different code paths. The former is called when a device is removed from the bus, while the latter is called at system shutdown time to quiesce the device. This means that some overlap exists between the two, because both have to take care of properly shutting down the hardware. But currently the logic used in these two callbacks isn't consistent in msm drivers, which could lead to kernel panic. For example, on .remove the component is deleted and its .unbind callback leads to the hardware being shutdown but only if the DRM device has been marked as registered. That check doesn't exist in the .shutdown logic and this can lead to the driver calling drm_atomic_helper_shutdown() for a DRM device that hasn't been properly initialized. A situation like this can happen if drivers for expected sub-devices fai... | 0% Низкий | около 1 года назад | ||
CVE-2022-50260 In the Linux kernel, the following vulnerability has been resolved: drm/msm: Make .remove and .shutdown HW shutdown consistent Drivers' .remove and .shutdown callbacks are executed on different code paths. The former is called when a device is removed from the bus, while the latter is called at system shutdown time to quiesce the device. This means that some overlap exists between the two, because both have to take care of properly shutting down the hardware. But currently the logic used in these two callbacks isn't consistent in msm drivers, which could lead to kernel panic. For example, on .remove the component is deleted and its .unbind callback leads to the hardware being shutdown but only if the DRM device has been marked as registered. That check doesn't exist in the .shutdown logic and this can lead to the driver calling drm_atomic_helper_shutdown() for a DRM device that hasn't been properly initialized. A situation like this can happen if drivers for expected sub-devices | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2022-50260 drm/msm: Make .remove and .shutdown HW shutdown consistent | CVSS3: 5.5 | 0% Низкий | 12 месяцев назад | |
CVE-2022-50260 In the Linux kernel, the following vulnerability has been resolved: d ... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
GHSA-wv25-jjx7-r2r4 In the Linux kernel, the following vulnerability has been resolved: drm/msm: Make .remove and .shutdown HW shutdown consistent Drivers' .remove and .shutdown callbacks are executed on different code paths. The former is called when a device is removed from the bus, while the latter is called at system shutdown time to quiesce the device. This means that some overlap exists between the two, because both have to take care of properly shutting down the hardware. But currently the logic used in these two callbacks isn't consistent in msm drivers, which could lead to kernel panic. For example, on .remove the component is deleted and its .unbind callback leads to the hardware being shutdown but only if the DRM device has been marked as registered. That check doesn't exist in the .shutdown logic and this can lead to the driver calling drm_atomic_helper_shutdown() for a DRM device that hasn't been properly initialized. A situation like this can happen if drivers for expected sub-devic... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
BDU:2026-08817 Уязвимость функции msm_drv_shutdown() модуля drivers/gpu/drm/msm/msm_drv.c драйвера инфраструктуры прямого рендеринга (DRI) ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 4 лет назад | |
ALT-PU-2020-3058 ALT-PU-2020-3058: package `kernel-image-un-def` update to version 5.9.0-alt1 | CVSS3: 7.8 | около 6 лет назад | ||
SUSE-SU-2025:03626-1 Security update for the Linux Kernel | около 1 года назад | |||
ALT-PU-2022-2913 ALT-PU-2022-2913: package `kernel-image-un-def` update to version 5.19.17-alt1 | CVSS3: 8 | около 4 лет назад | ||
ALT-PU-2022-2925 ALT-PU-2022-2925: package `kernel-image-mp` update to version 6.0.4-alt1 | CVSS3: 8 | около 4 лет назад | ||
SUSE-SU-2025:03628-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03615-1 Security update for the Linux Kernel | около 1 года назад | |||
ALT-PU-2023-1741 ALT-PU-2023-1741: package `kernel-image-un-def` update to version 6.1.26-alt1 | CVSS3: 9.8 | больше 3 лет назад | ||
ALT-PU-2023-1684 ALT-PU-2023-1684: package `kernel-image-std-def` update to version 6.1.26-alt1 | CVSS3: 9.8 | больше 3 лет назад | ||
ALT-PU-2022-3371 ALT-PU-2022-3371: package `kernel-image-rpi-un` update to version 6.1.0-alt1 | CVSS3: 9.3 | почти 4 года назад | ||
ALT-PU-2022-3364 ALT-PU-2022-3364: package `kernel-image-rpi-un` update to version 6.1.0-alt1 | CVSS3: 9.3 | почти 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 лет назад |
Уязвимостей на страницу