Поиск уязвимостей
Количество 23
Количество 23
CVE-2024-57876
In the Linux kernel, the following vulnerability has been resolved: drm/dp_mst: Fix resetting msg rx state after topology removal If the MST topology is removed during the reception of an MST down reply or MST up request sideband message, the drm_dp_mst_topology_mgr::up_req_recv/down_rep_recv states could be reset from one thread via drm_dp_mst_topology_mgr_set_mst(false), racing with the reading/parsing of the message from another thread via drm_dp_mst_handle_down_rep() or drm_dp_mst_handle_up_req(). The race is possible since the reader/parser doesn't hold any lock while accessing the reception state. This in turn can lead to a memory corruption in the reader/parser as described by commit bd2fccac61b4 ("drm/dp_mst: Fix MST sideband message body length check"). Fix the above by resetting the message reception state if needed before reading/parsing a message. Another solution would be to hold the drm_dp_mst_topology_mgr::lock for the whole duration of the message reception/parsing i...
CVE-2024-57876
In the Linux kernel, the following vulnerability has been resolved: drm/dp_mst: Fix resetting msg rx state after topology removal If the MST topology is removed during the reception of an MST down reply or MST up request sideband message, the drm_dp_mst_topology_mgr::up_req_recv/down_rep_recv states could be reset from one thread via drm_dp_mst_topology_mgr_set_mst(false), racing with the reading/parsing of the message from another thread via drm_dp_mst_handle_down_rep() or drm_dp_mst_handle_up_req(). The race is possible since the reader/parser doesn't hold any lock while accessing the reception state. This in turn can lead to a memory corruption in the reader/parser as described by commit bd2fccac61b4 ("drm/dp_mst: Fix MST sideband message body length check"). Fix the above by resetting the message reception state if needed before reading/parsing a message. Another solution would be to hold the drm_dp_mst_topology_mgr::lock for the whole duration of the message reception/parsing i...
CVE-2024-57876
In the Linux kernel, the following vulnerability has been resolved: drm/dp_mst: Fix resetting msg rx state after topology removal If the MST topology is removed during the reception of an MST down reply or MST up request sideband message, the drm_dp_mst_topology_mgr::up_req_recv/down_rep_recv states could be reset from one thread via drm_dp_mst_topology_mgr_set_mst(false), racing with the reading/parsing of the message from another thread via drm_dp_mst_handle_down_rep() or drm_dp_mst_handle_up_req(). The race is possible since the reader/parser doesn't hold any lock while accessing the reception state. This in turn can lead to a memory corruption in the reader/parser as described by commit bd2fccac61b4 ("drm/dp_mst: Fix MST sideband message body length check"). Fix the above by resetting the message reception state if needed before reading/parsing a message. Another solution would be to hold the drm_dp_mst_topology_mgr::lock for the whole duration of the message reception/parsing i
CVE-2024-57876
drm/dp_mst: Fix resetting msg rx state after topology removal
CVE-2024-57876
In the Linux kernel, the following vulnerability has been resolved: d ...
GHSA-3gjf-8gc5-3w3x
In the Linux kernel, the following vulnerability has been resolved: drm/dp_mst: Fix resetting msg rx state after topology removal If the MST topology is removed during the reception of an MST down reply or MST up request sideband message, the drm_dp_mst_topology_mgr::up_req_recv/down_rep_recv states could be reset from one thread via drm_dp_mst_topology_mgr_set_mst(false), racing with the reading/parsing of the message from another thread via drm_dp_mst_handle_down_rep() or drm_dp_mst_handle_up_req(). The race is possible since the reader/parser doesn't hold any lock while accessing the reception state. This in turn can lead to a memory corruption in the reader/parser as described by commit bd2fccac61b4 ("drm/dp_mst: Fix MST sideband message body length check"). Fix the above by resetting the message reception state if needed before reading/parsing a message. Another solution would be to hold the drm_dp_mst_topology_mgr::lock for the whole duration of the message reception/parsin...
BDU:2025-04125
Уязвимость компонента drm/dp_mst ядра операционной системы Linux, позволяющая нарушителю получить доступ к конфиденциальным данным, нарушить их целостность, а также вызвать отказ в обслуживании
ROS-20260114-7313
Уязвимость kernel-lt
SUSE-SU-2025:0577-2
Security update for the Linux Kernel
SUSE-SU-2025:0577-1
Security update for the Linux Kernel
ALT-PU-2023-1434
ALT-PU-2023-1434: package `kernel-image-mp` update to version 6.2.4-alt1
ALT-PU-2024-17897
ALT-PU-2024-17897: package `kernel-image-6.6` update to version 6.6.66-alt1
SUSE-SU-2025:0428-1
Security update for the Linux Kernel
SUSE-SU-2025:0557-1
Security update for the Linux Kernel
SUSE-SU-2025:0499-1
Security update for the Linux Kernel
ALT-PU-2024-17881
ALT-PU-2024-17881: package `kernel-image-6.12` update to version 6.12.6-alt1
SUSE-SU-2025:0289-1
Security update for the Linux Kernel
ALT-PU-2024-18063
ALT-PU-2024-18063: package `kernel-image-un-def` update to version 6.1.121-alt1
ALT-PU-2024-17211
ALT-PU-2024-17211: package `kernel-image-pine` update to version 6.12.5-alt1
ELSA-2025-20530
ELSA-2025-20530: Unbreakable Enterprise kernel security update (IMPORTANT)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-57876 In the Linux kernel, the following vulnerability has been resolved: drm/dp_mst: Fix resetting msg rx state after topology removal If the MST topology is removed during the reception of an MST down reply or MST up request sideband message, the drm_dp_mst_topology_mgr::up_req_recv/down_rep_recv states could be reset from one thread via drm_dp_mst_topology_mgr_set_mst(false), racing with the reading/parsing of the message from another thread via drm_dp_mst_handle_down_rep() or drm_dp_mst_handle_up_req(). The race is possible since the reader/parser doesn't hold any lock while accessing the reception state. This in turn can lead to a memory corruption in the reader/parser as described by commit bd2fccac61b4 ("drm/dp_mst: Fix MST sideband message body length check"). Fix the above by resetting the message reception state if needed before reading/parsing a message. Another solution would be to hold the drm_dp_mst_topology_mgr::lock for the whole duration of the message reception/parsing i... | CVSS3: 7 | 0% Низкий | почти 2 года назад | |
CVE-2024-57876 In the Linux kernel, the following vulnerability has been resolved: drm/dp_mst: Fix resetting msg rx state after topology removal If the MST topology is removed during the reception of an MST down reply or MST up request sideband message, the drm_dp_mst_topology_mgr::up_req_recv/down_rep_recv states could be reset from one thread via drm_dp_mst_topology_mgr_set_mst(false), racing with the reading/parsing of the message from another thread via drm_dp_mst_handle_down_rep() or drm_dp_mst_handle_up_req(). The race is possible since the reader/parser doesn't hold any lock while accessing the reception state. This in turn can lead to a memory corruption in the reader/parser as described by commit bd2fccac61b4 ("drm/dp_mst: Fix MST sideband message body length check"). Fix the above by resetting the message reception state if needed before reading/parsing a message. Another solution would be to hold the drm_dp_mst_topology_mgr::lock for the whole duration of the message reception/parsing i... | CVSS3: 4.6 | 0% Низкий | почти 2 года назад | |
CVE-2024-57876 In the Linux kernel, the following vulnerability has been resolved: drm/dp_mst: Fix resetting msg rx state after topology removal If the MST topology is removed during the reception of an MST down reply or MST up request sideband message, the drm_dp_mst_topology_mgr::up_req_recv/down_rep_recv states could be reset from one thread via drm_dp_mst_topology_mgr_set_mst(false), racing with the reading/parsing of the message from another thread via drm_dp_mst_handle_down_rep() or drm_dp_mst_handle_up_req(). The race is possible since the reader/parser doesn't hold any lock while accessing the reception state. This in turn can lead to a memory corruption in the reader/parser as described by commit bd2fccac61b4 ("drm/dp_mst: Fix MST sideband message body length check"). Fix the above by resetting the message reception state if needed before reading/parsing a message. Another solution would be to hold the drm_dp_mst_topology_mgr::lock for the whole duration of the message reception/parsing i | CVSS3: 7 | 0% Низкий | почти 2 года назад | |
CVE-2024-57876 drm/dp_mst: Fix resetting msg rx state after topology removal | 0% Низкий | около 1 года назад | ||
CVE-2024-57876 In the Linux kernel, the following vulnerability has been resolved: d ... | CVSS3: 7 | 0% Низкий | почти 2 года назад | |
GHSA-3gjf-8gc5-3w3x In the Linux kernel, the following vulnerability has been resolved: drm/dp_mst: Fix resetting msg rx state after topology removal If the MST topology is removed during the reception of an MST down reply or MST up request sideband message, the drm_dp_mst_topology_mgr::up_req_recv/down_rep_recv states could be reset from one thread via drm_dp_mst_topology_mgr_set_mst(false), racing with the reading/parsing of the message from another thread via drm_dp_mst_handle_down_rep() or drm_dp_mst_handle_up_req(). The race is possible since the reader/parser doesn't hold any lock while accessing the reception state. This in turn can lead to a memory corruption in the reader/parser as described by commit bd2fccac61b4 ("drm/dp_mst: Fix MST sideband message body length check"). Fix the above by resetting the message reception state if needed before reading/parsing a message. Another solution would be to hold the drm_dp_mst_topology_mgr::lock for the whole duration of the message reception/parsin... | CVSS3: 7 | 0% Низкий | почти 2 года назад | |
BDU:2025-04125 Уязвимость компонента drm/dp_mst ядра операционной системы Linux, позволяющая нарушителю получить доступ к конфиденциальным данным, нарушить их целостность, а также вызвать отказ в обслуживании | CVSS3: 7 | 0% Низкий | почти 2 года назад | |
ROS-20260114-7313 Уязвимость kernel-lt | CVSS3: 7 | 0% Низкий | 10 месяцев назад | |
SUSE-SU-2025:0577-2 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:0577-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2023-1434 ALT-PU-2023-1434: package `kernel-image-mp` update to version 6.2.4-alt1 | CVSS3: 8.8 | больше 3 лет назад | ||
ALT-PU-2024-17897 ALT-PU-2024-17897: package `kernel-image-6.6` update to version 6.6.66-alt1 | CVSS3: 9.1 | больше 1 года назад | ||
SUSE-SU-2025:0428-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:0557-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:0499-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2024-17881 ALT-PU-2024-17881: package `kernel-image-6.12` update to version 6.12.6-alt1 | CVSS3: 9.1 | больше 1 года назад | ||
SUSE-SU-2025:0289-1 Security update for the Linux Kernel | почти 2 года назад | |||
ALT-PU-2024-18063 ALT-PU-2024-18063: package `kernel-image-un-def` update to version 6.1.121-alt1 | CVSS3: 9.8 | почти 2 года назад | ||
ALT-PU-2024-17211 ALT-PU-2024-17211: package `kernel-image-pine` update to version 6.12.5-alt1 | CVSS3: 9.8 | почти 2 года назад | ||
ELSA-2025-20530 ELSA-2025-20530: Unbreakable Enterprise kernel security update (IMPORTANT) | около 1 года назад |
Уязвимостей на страницу