Поиск уязвимостей
Количество 23
Количество 23
CVE-2024-26687
In the Linux kernel, the following vulnerability has been resolved: xen/events: close evtchn after mapping cleanup shutdown_pirq and startup_pirq are not taking the irq_mapping_update_lock because they can't due to lock inversion. Both are called with the irq_desc->lock being taking. The lock order, however, is first irq_mapping_update_lock and then irq_desc->lock. This opens multiple races: - shutdown_pirq can be interrupted by a function that allocates an event channel: CPU0 CPU1 shutdown_pirq { xen_evtchn_close(e) __startup_pirq { EVTCHNOP_bind_pirq -> returns just freed evtchn e set_evtchn_to_irq(e, irq) } xen_irq_info_cleanup() { set_evtchn_to_irq(e, -1) } } Assume here event channel e refers here to the same event channel number. After this race the evtchn_to_irq mapping for e is invalid (-1). - __startup_pirq races with __unbind_from_irq in a similar way. Because __startup_pirq doesn't take irq_mapping_update_lock it can grab the evtchn that __unbind_fr...
CVE-2024-26687
In the Linux kernel, the following vulnerability has been resolved: xen/events: close evtchn after mapping cleanup shutdown_pirq and startup_pirq are not taking the irq_mapping_update_lock because they can't due to lock inversion. Both are called with the irq_desc->lock being taking. The lock order, however, is first irq_mapping_update_lock and then irq_desc->lock. This opens multiple races: - shutdown_pirq can be interrupted by a function that allocates an event channel: CPU0 CPU1 shutdown_pirq { xen_evtchn_close(e) __startup_pirq { EVTCHNOP_bind_pirq -> returns just freed evtchn e set_evtchn_to_irq(e, irq) } xen_irq_info_cleanup() { set_evtchn_to_irq(e, -1) } } Assume here event channel e refers here to the same event channel number. After this race the evtchn_to_irq mapping for e is invalid (-1). - __startup_pirq races with __unbind_from_irq in a similar way. Because __startup_pirq doesn't take irq_mapping_update_lock it can grab the evtchn that __unbind_fr...
CVE-2024-26687
In the Linux kernel, the following vulnerability has been resolved: xen/events: close evtchn after mapping cleanup shutdown_pirq and startup_pirq are not taking the irq_mapping_update_lock because they can't due to lock inversion. Both are called with the irq_desc->lock being taking. The lock order, however, is first irq_mapping_update_lock and then irq_desc->lock. This opens multiple races: - shutdown_pirq can be interrupted by a function that allocates an event channel: CPU0 CPU1 shutdown_pirq { xen_evtchn_close(e) __startup_pirq { EVTCHNOP_bind_pirq -> returns just freed evtchn e set_evtchn_to_irq(e, irq) } xen_irq_info_cleanup() { set_evtchn_to_irq(e, -1) } } Assume here event channel e refers here to the same event channel number. After this race the evtchn_to_irq ma
CVE-2024-26687
xen/events: close evtchn after mapping cleanup
CVE-2024-26687
In the Linux kernel, the following vulnerability has been resolved: x ...
GHSA-7xq6-jm62-ww8g
In the Linux kernel, the following vulnerability has been resolved: xen/events: close evtchn after mapping cleanup shutdown_pirq and startup_pirq are not taking the irq_mapping_update_lock because they can't due to lock inversion. Both are called with the irq_desc->lock being taking. The lock order, however, is first irq_mapping_update_lock and then irq_desc->lock. This opens multiple races: - shutdown_pirq can be interrupted by a function that allocates an event channel: CPU0 CPU1 shutdown_pirq { xen_evtchn_close(e) __startup_pirq { EVTCHNOP_bind_pirq -> returns just freed evtchn e set_evtchn_to_irq(e, irq) } xen_irq_info_cleanup() { set_evtchn_to_irq(e, -1) } } Assume here event channel e refers here to the same event channel number. After this race the evtchn_to_irq...
BDU:2025-03932
Уязвимость компонента events_base.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20241016-02
Множественные уязвимости kernel-lt
ALT-PU-2024-18363
ALT-PU-2024-18363: package `kernel-image-std-def` update to version 6.1.81-alt1
ALT-PU-2024-18056
ALT-PU-2024-18056: package `kernel-image-un-def` update to version 6.1.81-alt1
SUSE-SU-2024:1641-1
Security update for the Linux Kernel
ALT-PU-2024-18256
ALT-PU-2024-18256: package `kernel-image-rt` update to version 6.1.82-alt1.rt27
ALT-PU-2024-18465
ALT-PU-2024-18465: package `kernel-image-un-def` update to version 6.6.19-alt1
ALT-PU-2024-18208
ALT-PU-2024-18208: package `kernel-image-pine` update to version 6.6.20-alt1
SUSE-SU-2024:2381-1
Security update for the Linux Kernel
SUSE-SU-2024:2360-1
Security update for the Linux Kernel
SUSE-SU-2024:2561-1
Security update for the Linux Kernel
SUSE-SU-2024:1644-1
Security update for the Linux Kernel
SUSE-SU-2024:1659-1
Security update for the Linux Kernel
SUSE-SU-2024:1663-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-26687 In the Linux kernel, the following vulnerability has been resolved: xen/events: close evtchn after mapping cleanup shutdown_pirq and startup_pirq are not taking the irq_mapping_update_lock because they can't due to lock inversion. Both are called with the irq_desc->lock being taking. The lock order, however, is first irq_mapping_update_lock and then irq_desc->lock. This opens multiple races: - shutdown_pirq can be interrupted by a function that allocates an event channel: CPU0 CPU1 shutdown_pirq { xen_evtchn_close(e) __startup_pirq { EVTCHNOP_bind_pirq -> returns just freed evtchn e set_evtchn_to_irq(e, irq) } xen_irq_info_cleanup() { set_evtchn_to_irq(e, -1) } } Assume here event channel e refers here to the same event channel number. After this race the evtchn_to_irq mapping for e is invalid (-1). - __startup_pirq races with __unbind_from_irq in a similar way. Because __startup_pirq doesn't take irq_mapping_update_lock it can grab the evtchn that __unbind_fr... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26687 In the Linux kernel, the following vulnerability has been resolved: xen/events: close evtchn after mapping cleanup shutdown_pirq and startup_pirq are not taking the irq_mapping_update_lock because they can't due to lock inversion. Both are called with the irq_desc->lock being taking. The lock order, however, is first irq_mapping_update_lock and then irq_desc->lock. This opens multiple races: - shutdown_pirq can be interrupted by a function that allocates an event channel: CPU0 CPU1 shutdown_pirq { xen_evtchn_close(e) __startup_pirq { EVTCHNOP_bind_pirq -> returns just freed evtchn e set_evtchn_to_irq(e, irq) } xen_irq_info_cleanup() { set_evtchn_to_irq(e, -1) } } Assume here event channel e refers here to the same event channel number. After this race the evtchn_to_irq mapping for e is invalid (-1). - __startup_pirq races with __unbind_from_irq in a similar way. Because __startup_pirq doesn't take irq_mapping_update_lock it can grab the evtchn that __unbind_fr... | CVSS3: 4.4 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26687 In the Linux kernel, the following vulnerability has been resolved: xen/events: close evtchn after mapping cleanup shutdown_pirq and startup_pirq are not taking the irq_mapping_update_lock because they can't due to lock inversion. Both are called with the irq_desc->lock being taking. The lock order, however, is first irq_mapping_update_lock and then irq_desc->lock. This opens multiple races: - shutdown_pirq can be interrupted by a function that allocates an event channel: CPU0 CPU1 shutdown_pirq { xen_evtchn_close(e) __startup_pirq { EVTCHNOP_bind_pirq -> returns just freed evtchn e set_evtchn_to_irq(e, irq) } xen_irq_info_cleanup() { set_evtchn_to_irq(e, -1) } } Assume here event channel e refers here to the same event channel number. After this race the evtchn_to_irq ma | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26687 xen/events: close evtchn after mapping cleanup | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
CVE-2024-26687 In the Linux kernel, the following vulnerability has been resolved: x ... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
GHSA-7xq6-jm62-ww8g In the Linux kernel, the following vulnerability has been resolved: xen/events: close evtchn after mapping cleanup shutdown_pirq and startup_pirq are not taking the irq_mapping_update_lock because they can't due to lock inversion. Both are called with the irq_desc->lock being taking. The lock order, however, is first irq_mapping_update_lock and then irq_desc->lock. This opens multiple races: - shutdown_pirq can be interrupted by a function that allocates an event channel: CPU0 CPU1 shutdown_pirq { xen_evtchn_close(e) __startup_pirq { EVTCHNOP_bind_pirq -> returns just freed evtchn e set_evtchn_to_irq(e, irq) } xen_irq_info_cleanup() { set_evtchn_to_irq(e, -1) } } Assume here event channel e refers here to the same event channel number. After this race the evtchn_to_irq... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
BDU:2025-03932 Уязвимость компонента events_base.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | почти 3 года назад | |
ROS-20241016-02 Множественные уязвимости kernel-lt | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2024-18363 ALT-PU-2024-18363: package `kernel-image-std-def` update to version 6.1.81-alt1 | CVSS3: 8.8 | больше 2 лет назад | ||
ALT-PU-2024-18056 ALT-PU-2024-18056: package `kernel-image-un-def` update to version 6.1.81-alt1 | CVSS3: 8.8 | больше 2 лет назад | ||
SUSE-SU-2024:1641-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2024-18256 ALT-PU-2024-18256: package `kernel-image-rt` update to version 6.1.82-alt1.rt27 | CVSS3: 8.8 | больше 2 лет назад | ||
ALT-PU-2024-18465 ALT-PU-2024-18465: package `kernel-image-un-def` update to version 6.6.19-alt1 | CVSS3: 8.8 | больше 2 лет назад | ||
ALT-PU-2024-18208 ALT-PU-2024-18208: package `kernel-image-pine` update to version 6.6.20-alt1 | CVSS3: 8.8 | больше 2 лет назад | ||
SUSE-SU-2024:2381-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:2360-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:2561-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:1644-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:1659-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:1663-1 Security update for the Linux Kernel | больше 2 лет назад |
Уязвимостей на страницу