Поиск уязвимостей
Количество 23
Количество 23
CVE-2022-48675
In the Linux kernel, the following vulnerability has been resolved: IB/core: Fix a nested dead lock as part of ODP flow Fix a nested dead lock as part of ODP flow by using mmput_async(). From the below call trace [1] can see that calling mmput() once we have the umem_odp->umem_mutex locked as required by ib_umem_odp_map_dma_and_lock() might trigger in the same task the exit_mmap()->__mmu_notifier_release()->mlx5_ib_invalidate_range() which may dead lock when trying to lock the same mutex. Moving to use mmput_async() will solve the problem as the above exit_mmap() flow will be called in other task and will be executed once the lock will be available. [1] [64843.077665] task:kworker/u133:2 state:D stack: 0 pid:80906 ppid: 2 flags:0x00004000 [64843.077672] Workqueue: mlx5_ib_page_fault mlx5_ib_eqe_pf_action [mlx5_ib] [64843.077719] Call Trace: [64843.077722] <TASK> [64843.077724] __schedule+0x23d/0x590 [64843.077729] schedule+0x4e/0xb0 [64843.077735] schedule_preempt_disabled+0...
CVE-2022-48675
In the Linux kernel, the following vulnerability has been resolved: IB/core: Fix a nested dead lock as part of ODP flow Fix a nested dead lock as part of ODP flow by using mmput_async(). From the below call trace [1] can see that calling mmput() once we have the umem_odp->umem_mutex locked as required by ib_umem_odp_map_dma_and_lock() might trigger in the same task the exit_mmap()->__mmu_notifier_release()->mlx5_ib_invalidate_range() which may dead lock when trying to lock the same mutex. Moving to use mmput_async() will solve the problem as the above exit_mmap() flow will be called in other task and will be executed once the lock will be available. [1] [64843.077665] task:kworker/u133:2 state:D stack: 0 pid:80906 ppid: 2 flags:0x00004000 [64843.077672] Workqueue: mlx5_ib_page_fault mlx5_ib_eqe_pf_action [mlx5_ib] [64843.077719] Call Trace: [64843.077722] <TASK> [64843.077724] __schedule+0x23d/0x590 [64843.077729] schedule+0x4e/0xb0 [64843.077735] schedule_preempt_disabled+0...
CVE-2022-48675
In the Linux kernel, the following vulnerability has been resolved: IB/core: Fix a nested dead lock as part of ODP flow Fix a nested dead lock as part of ODP flow by using mmput_async(). From the below call trace [1] can see that calling mmput() once we have the umem_odp->umem_mutex locked as required by ib_umem_odp_map_dma_and_lock() might trigger in the same task the exit_mmap()->__mmu_notifier_release()->mlx5_ib_invalidate_range() which may dead lock when trying to lock the same mutex. Moving to use mmput_async() will solve the problem as the above exit_mmap() flow will be called in other task and will be executed once the lock will be available. [1] [64843.077665] task:kworker/u133:2 state:D stack: 0 pid:80906 ppid: 2 flags:0x00004000 [64843.077672] Workqueue: mlx5_ib_page_fault mlx5_ib_eqe_pf_action [mlx5_ib] [64843.077719] Call Trace: [64843.077722] <TASK> [64843.077724] __schedule+0x23d/0x590 [64843.077729] schedule+0x4e/0xb0 [64843.077735] schedule_preempt_disabled
CVE-2022-48675
In the Linux kernel, the following vulnerability has been resolved: I ...
GHSA-c34q-8xrw-g745
In the Linux kernel, the following vulnerability has been resolved: IB/core: Fix a nested dead lock as part of ODP flow Fix a nested dead lock as part of ODP flow by using mmput_async(). From the below call trace [1] can see that calling mmput() once we have the umem_odp->umem_mutex locked as required by ib_umem_odp_map_dma_and_lock() might trigger in the same task the exit_mmap()->__mmu_notifier_release()->mlx5_ib_invalidate_range() which may dead lock when trying to lock the same mutex. Moving to use mmput_async() will solve the problem as the above exit_mmap() flow will be called in other task and will be executed once the lock will be available. [1] [64843.077665] task:kworker/u133:2 state:D stack: 0 pid:80906 ppid: 2 flags:0x00004000 [64843.077672] Workqueue: mlx5_ib_page_fault mlx5_ib_eqe_pf_action [mlx5_ib] [64843.077719] Call Trace: [64843.077722] <TASK> [64843.077724] __schedule+0x23d/0x590 [64843.077729] schedule+0x4e/0xb0 [64843.077735] schedule_preempt_disab...
BDU:2024-06338
Уязвимость функции mmput() в компоненте IB/core ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20240814-03
Множественные уязвимости kernel-lt
ALT-PU-2022-7811
ALT-PU-2022-7811: package `kernel-image-std-def` update to version 5.15.68-alt1
ALT-PU-2022-2621
ALT-PU-2022-2621: package `kernel-image-un-def` update to version 5.19.9-alt1
ALT-PU-2022-2681
ALT-PU-2022-2681: package `kernel-image-rt` update to version 5.10.145-alt1.rt74
ALT-PU-2022-2680
ALT-PU-2022-2680: package `kernel-image-rt` update to version 5.10.145-alt1.rt74
ALT-PU-2022-2658
ALT-PU-2022-2658: package `kernel-image-std-def` update to version 5.10.143-alt1
ALT-PU-2022-2691
ALT-PU-2022-2691: package `kernel-image-mp` update to version 5.19.12-alt1
ALT-PU-2022-2641
ALT-PU-2022-2641: package `kernel-image-un-def` update to version 5.15.68-alt1
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
SUSE-SU-2024:2189-1
Security update for the Linux Kernel
ALT-PU-2022-2664
ALT-PU-2022-2664: package `kernel-image-std-kvm` update to version 5.10.144-alt1
ALT-PU-2022-2692
ALT-PU-2022-2692: package `kernel-image-rpi-def` update to version 5.15.70-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2022-48675 In the Linux kernel, the following vulnerability has been resolved: IB/core: Fix a nested dead lock as part of ODP flow Fix a nested dead lock as part of ODP flow by using mmput_async(). From the below call trace [1] can see that calling mmput() once we have the umem_odp->umem_mutex locked as required by ib_umem_odp_map_dma_and_lock() might trigger in the same task the exit_mmap()->__mmu_notifier_release()->mlx5_ib_invalidate_range() which may dead lock when trying to lock the same mutex. Moving to use mmput_async() will solve the problem as the above exit_mmap() flow will be called in other task and will be executed once the lock will be available. [1] [64843.077665] task:kworker/u133:2 state:D stack: 0 pid:80906 ppid: 2 flags:0x00004000 [64843.077672] Workqueue: mlx5_ib_page_fault mlx5_ib_eqe_pf_action [mlx5_ib] [64843.077719] Call Trace: [64843.077722] <TASK> [64843.077724] __schedule+0x23d/0x590 [64843.077729] schedule+0x4e/0xb0 [64843.077735] schedule_preempt_disabled+0... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2022-48675 In the Linux kernel, the following vulnerability has been resolved: IB/core: Fix a nested dead lock as part of ODP flow Fix a nested dead lock as part of ODP flow by using mmput_async(). From the below call trace [1] can see that calling mmput() once we have the umem_odp->umem_mutex locked as required by ib_umem_odp_map_dma_and_lock() might trigger in the same task the exit_mmap()->__mmu_notifier_release()->mlx5_ib_invalidate_range() which may dead lock when trying to lock the same mutex. Moving to use mmput_async() will solve the problem as the above exit_mmap() flow will be called in other task and will be executed once the lock will be available. [1] [64843.077665] task:kworker/u133:2 state:D stack: 0 pid:80906 ppid: 2 flags:0x00004000 [64843.077672] Workqueue: mlx5_ib_page_fault mlx5_ib_eqe_pf_action [mlx5_ib] [64843.077719] Call Trace: [64843.077722] <TASK> [64843.077724] __schedule+0x23d/0x590 [64843.077729] schedule+0x4e/0xb0 [64843.077735] schedule_preempt_disabled+0... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2022-48675 In the Linux kernel, the following vulnerability has been resolved: IB/core: Fix a nested dead lock as part of ODP flow Fix a nested dead lock as part of ODP flow by using mmput_async(). From the below call trace [1] can see that calling mmput() once we have the umem_odp->umem_mutex locked as required by ib_umem_odp_map_dma_and_lock() might trigger in the same task the exit_mmap()->__mmu_notifier_release()->mlx5_ib_invalidate_range() which may dead lock when trying to lock the same mutex. Moving to use mmput_async() will solve the problem as the above exit_mmap() flow will be called in other task and will be executed once the lock will be available. [1] [64843.077665] task:kworker/u133:2 state:D stack: 0 pid:80906 ppid: 2 flags:0x00004000 [64843.077672] Workqueue: mlx5_ib_page_fault mlx5_ib_eqe_pf_action [mlx5_ib] [64843.077719] Call Trace: [64843.077722] <TASK> [64843.077724] __schedule+0x23d/0x590 [64843.077729] schedule+0x4e/0xb0 [64843.077735] schedule_preempt_disabled | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2022-48675 In the Linux kernel, the following vulnerability has been resolved: I ... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
GHSA-c34q-8xrw-g745 In the Linux kernel, the following vulnerability has been resolved: IB/core: Fix a nested dead lock as part of ODP flow Fix a nested dead lock as part of ODP flow by using mmput_async(). From the below call trace [1] can see that calling mmput() once we have the umem_odp->umem_mutex locked as required by ib_umem_odp_map_dma_and_lock() might trigger in the same task the exit_mmap()->__mmu_notifier_release()->mlx5_ib_invalidate_range() which may dead lock when trying to lock the same mutex. Moving to use mmput_async() will solve the problem as the above exit_mmap() flow will be called in other task and will be executed once the lock will be available. [1] [64843.077665] task:kworker/u133:2 state:D stack: 0 pid:80906 ppid: 2 flags:0x00004000 [64843.077672] Workqueue: mlx5_ib_page_fault mlx5_ib_eqe_pf_action [mlx5_ib] [64843.077719] Call Trace: [64843.077722] <TASK> [64843.077724] __schedule+0x23d/0x590 [64843.077729] schedule+0x4e/0xb0 [64843.077735] schedule_preempt_disab... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
BDU:2024-06338 Уязвимость функции mmput() в компоненте IB/core ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | около 4 лет назад | |
ROS-20240814-03 Множественные уязвимости kernel-lt | CVSS3: 7.8 | около 2 лет назад | ||
ALT-PU-2022-7811 ALT-PU-2022-7811: package `kernel-image-std-def` update to version 5.15.68-alt1 | CVSS3: 9.8 | около 4 лет назад | ||
ALT-PU-2022-2621 ALT-PU-2022-2621: package `kernel-image-un-def` update to version 5.19.9-alt1 | CVSS3: 9.8 | около 4 лет назад | ||
ALT-PU-2022-2681 ALT-PU-2022-2681: package `kernel-image-rt` update to version 5.10.145-alt1.rt74 | CVSS3: 9.8 | около 4 лет назад | ||
ALT-PU-2022-2680 ALT-PU-2022-2680: package `kernel-image-rt` update to version 5.10.145-alt1.rt74 | CVSS3: 9.8 | около 4 лет назад | ||
ALT-PU-2022-2658 ALT-PU-2022-2658: package `kernel-image-std-def` update to version 5.10.143-alt1 | CVSS3: 9.8 | около 4 лет назад | ||
ALT-PU-2022-2691 ALT-PU-2022-2691: package `kernel-image-mp` update to version 5.19.12-alt1 | CVSS3: 9.8 | около 4 лет назад | ||
ALT-PU-2022-2641 ALT-PU-2022-2641: package `kernel-image-un-def` update to version 5.15.68-alt1 | CVSS3: 9.8 | около 4 лет назад | ||
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 лет назад | |||
SUSE-SU-2024:2189-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2022-2664 ALT-PU-2022-2664: package `kernel-image-std-kvm` update to version 5.10.144-alt1 | CVSS3: 9.8 | около 4 лет назад | ||
ALT-PU-2022-2692 ALT-PU-2022-2692: package `kernel-image-rpi-def` update to version 5.15.70-alt1 | CVSS3: 10 | около 4 лет назад |
Уязвимостей на страницу