Поиск уязвимостей
Количество 21
Количество 21
CVE-2024-27022
In the Linux kernel, the following vulnerability has been resolved: fork: defer linking file vma until vma is fully initialized Thorvald reported a WARNING [1]. And the root cause is below race: CPU 1 CPU 2 fork hugetlbfs_fallocate dup_mmap hugetlbfs_punch_hole i_mmap_lock_write(mapping); vma_interval_tree_insert_after -- Child vma is visible through i_mmap tree. i_mmap_unlock_write(mapping); hugetlb_dup_vma_private -- Clear vma_lock outside i_mmap_rwsem! i_mmap_lock_write(mapping); hugetlb_vmdelete_list vma_interval_tree_foreach hugetlb_vma_trylock_write -- Vma_lock is cleared. tmp->vm_ops->open -- Alloc new vma_lock outside i_mmap_rwsem! hugetlb_vma_unlock_write -- Vma_lock is assigned!!! i_mmap_unlock_write(mapping); hugetlb_dup_vma_private() and hugetlb_vm_op_open() are called outside i_mmap_rwsem lock while vma lock can be used in the same time. Fix this by deferring linking file vma until vma is fully initialized. Those vmas should be initialized first before the...
CVE-2024-27022
In the Linux kernel, the following vulnerability has been resolved: fork: defer linking file vma until vma is fully initialized Thorvald reported a WARNING [1]. And the root cause is below race: CPU 1CPU 2 forkhugetlbfs_fallocate dup_mmap hugetlbfs_punch_hole i_mmap_lock_write(mapping); vma_interval_tree_insert_after -- Child vma is visible through i_mmap tree. i_mmap_unlock_write(mapping); hugetlb_dup_vma_private -- Clear vma_lock outside i_mmap_rwsem! i_mmap_lock_write(mapping); hugetlb_vmdelete_list vma_interval_tree_foreach hugetlb_vma_trylock_write -- Vma_lock is cleared. tmp->vm_ops->open -- Alloc new vma_lock outside i_mmap_rwsem! hugetlb_vma_unlock_write -- Vma_lock is assigned!!! i_mmap_unlock_write(mapping); hugetlb_dup_vma_private() and hugetlb_vm_op_open() are called outside i_mmap_rwsem lock while vma lock can be used in the same time. Fix this by deferring linking file vma until vma is fully initialized. Those vmas should be initialized first before they can be used.
CVE-2024-27022
In the Linux kernel, the following vulnerability has been resolved: fork: defer linking file vma until vma is fully initialized Thorvald reported a WARNING [1]. And the root cause is below race: CPU 1 CPU 2 fork hugetlbfs_fallocate dup_mmap hugetlbfs_punch_hole i_mmap_lock_write(mapping); vma_interval_tree_insert_after -- Child vma is visible through i_mmap tree. i_mmap_unlock_write(mapping); hugetlb_dup_vma_private -- Clear vma_lock outside i_mmap_rwsem! i_mmap_lock_write(mapping); hugetlb_vmdelete_list vma_interval_tree_foreach hugetlb_vma_trylock_write -- Vma_lock is cleared. tmp->vm_ops->open -- Alloc new vma_lock outside i_mmap_rwsem! hugetlb_vma_unlock_write -- Vma_lock is assigned!!! i_mmap_unlock_write(mapping); hugetlb_dup_vma_private() and hugetlb_vm_op_open() are called outside i_mmap_rwsem lock while vma lock can be used in the same time. Fix this by deferring linking file vma until vma is fully
CVE-2024-27022
fork: defer linking file vma until vma is fully initialized
CVE-2024-27022
In the Linux kernel, the following vulnerability has been resolved: f ...
GHSA-rvcc-g859-q9qh
In the Linux kernel, the following vulnerability has been resolved: fork: defer linking file vma until vma is fully initialized Thorvald reported a WARNING [1]. And the root cause is below race: CPU 1 CPU 2 fork hugetlbfs_fallocate dup_mmap hugetlbfs_punch_hole i_mmap_lock_write(mapping); vma_interval_tree_insert_after -- Child vma is visible through i_mmap tree. i_mmap_unlock_write(mapping); hugetlb_dup_vma_private -- Clear vma_lock outside i_mmap_rwsem! i_mmap_lock_write(mapping); hugetlb_vmdelete_list vma_interval_tree_foreach hugetlb_vma_trylock_write -- Vma_lock is cleared. tmp->vm_ops->open -- Alloc new vma_lock outside i_mmap_rwsem! hugetlb_vma_unlock_write -- Vma_lock is assigned!!! i_mmap_unlock_write(mapping); hugetlb_dup_vma_private() and hugetlb_vm_op_open() are called outside i_mmap_rwsem lock while vma lock can be used in the same time. Fix this by deferring linking file vma until vma is fu...
BDU:2024-04584
Уязвимость функции dup_mmap() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
ELSA-2024-6997
ELSA-2024-6997: kernel security update (IMPORTANT)
ROS-20241101-02
Множественные уязвимости kernel-lt
ALT-PU-2024-18371
ALT-PU-2024-18371: package `kernel-image-std-def` update to version 6.1.90-alt1
ALT-PU-2024-18473
ALT-PU-2024-18473: package `kernel-image-un-def` update to version 6.6.30-alt1
ALT-PU-2024-7242
ALT-PU-2024-7242: package `kernel-image-6.8` update to version 6.8.8-alt1
ALT-PU-2024-18214
ALT-PU-2024-18214: package `kernel-image-pine` update to version 6.6.30-alt1
ALT-PU-2024-17905
ALT-PU-2024-17905: package `kernel-image-un-def` update to version 6.1.90-alt1
ALT-PU-2024-18118
ALT-PU-2024-18118: package `kernel-image-mp` update to version 6.8.8-alt1
ALT-PU-2024-7646
ALT-PU-2024-7646: package `kernel-image-rt` update to version 6.1.90-alt1.rt30
SUSE-SU-2024:2203-1
Security update for the Linux Kernel
SUSE-SU-2024:2135-1
Security update for the Linux Kernel
ALT-PU-2024-13979
ALT-PU-2024-13979: package `kernel-image-rpi-un` update to version 6.6.56-alt1
SUSE-SU-2024:2973-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-27022 In the Linux kernel, the following vulnerability has been resolved: fork: defer linking file vma until vma is fully initialized Thorvald reported a WARNING [1]. And the root cause is below race: CPU 1 CPU 2 fork hugetlbfs_fallocate dup_mmap hugetlbfs_punch_hole i_mmap_lock_write(mapping); vma_interval_tree_insert_after -- Child vma is visible through i_mmap tree. i_mmap_unlock_write(mapping); hugetlb_dup_vma_private -- Clear vma_lock outside i_mmap_rwsem! i_mmap_lock_write(mapping); hugetlb_vmdelete_list vma_interval_tree_foreach hugetlb_vma_trylock_write -- Vma_lock is cleared. tmp->vm_ops->open -- Alloc new vma_lock outside i_mmap_rwsem! hugetlb_vma_unlock_write -- Vma_lock is assigned!!! i_mmap_unlock_write(mapping); hugetlb_dup_vma_private() and hugetlb_vm_op_open() are called outside i_mmap_rwsem lock while vma lock can be used in the same time. Fix this by deferring linking file vma until vma is fully initialized. Those vmas should be initialized first before the... | CVSS3: 7.8 | 0% Низкий | больше 2 лет назад | |
CVE-2024-27022 In the Linux kernel, the following vulnerability has been resolved: fork: defer linking file vma until vma is fully initialized Thorvald reported a WARNING [1]. And the root cause is below race: CPU 1CPU 2 forkhugetlbfs_fallocate dup_mmap hugetlbfs_punch_hole i_mmap_lock_write(mapping); vma_interval_tree_insert_after -- Child vma is visible through i_mmap tree. i_mmap_unlock_write(mapping); hugetlb_dup_vma_private -- Clear vma_lock outside i_mmap_rwsem! i_mmap_lock_write(mapping); hugetlb_vmdelete_list vma_interval_tree_foreach hugetlb_vma_trylock_write -- Vma_lock is cleared. tmp->vm_ops->open -- Alloc new vma_lock outside i_mmap_rwsem! hugetlb_vma_unlock_write -- Vma_lock is assigned!!! i_mmap_unlock_write(mapping); hugetlb_dup_vma_private() and hugetlb_vm_op_open() are called outside i_mmap_rwsem lock while vma lock can be used in the same time. Fix this by deferring linking file vma until vma is fully initialized. Those vmas should be initialized first before they can be used. | CVSS3: 4.7 | 0% Низкий | больше 2 лет назад | |
CVE-2024-27022 In the Linux kernel, the following vulnerability has been resolved: fork: defer linking file vma until vma is fully initialized Thorvald reported a WARNING [1]. And the root cause is below race: CPU 1 CPU 2 fork hugetlbfs_fallocate dup_mmap hugetlbfs_punch_hole i_mmap_lock_write(mapping); vma_interval_tree_insert_after -- Child vma is visible through i_mmap tree. i_mmap_unlock_write(mapping); hugetlb_dup_vma_private -- Clear vma_lock outside i_mmap_rwsem! i_mmap_lock_write(mapping); hugetlb_vmdelete_list vma_interval_tree_foreach hugetlb_vma_trylock_write -- Vma_lock is cleared. tmp->vm_ops->open -- Alloc new vma_lock outside i_mmap_rwsem! hugetlb_vma_unlock_write -- Vma_lock is assigned!!! i_mmap_unlock_write(mapping); hugetlb_dup_vma_private() and hugetlb_vm_op_open() are called outside i_mmap_rwsem lock while vma lock can be used in the same time. Fix this by deferring linking file vma until vma is fully | CVSS3: 7.8 | 0% Низкий | больше 2 лет назад | |
CVE-2024-27022 fork: defer linking file vma until vma is fully initialized | CVSS3: 7.8 | 0% Низкий | около 2 лет назад | |
CVE-2024-27022 In the Linux kernel, the following vulnerability has been resolved: f ... | CVSS3: 7.8 | 0% Низкий | больше 2 лет назад | |
GHSA-rvcc-g859-q9qh In the Linux kernel, the following vulnerability has been resolved: fork: defer linking file vma until vma is fully initialized Thorvald reported a WARNING [1]. And the root cause is below race: CPU 1 CPU 2 fork hugetlbfs_fallocate dup_mmap hugetlbfs_punch_hole i_mmap_lock_write(mapping); vma_interval_tree_insert_after -- Child vma is visible through i_mmap tree. i_mmap_unlock_write(mapping); hugetlb_dup_vma_private -- Clear vma_lock outside i_mmap_rwsem! i_mmap_lock_write(mapping); hugetlb_vmdelete_list vma_interval_tree_foreach hugetlb_vma_trylock_write -- Vma_lock is cleared. tmp->vm_ops->open -- Alloc new vma_lock outside i_mmap_rwsem! hugetlb_vma_unlock_write -- Vma_lock is assigned!!! i_mmap_unlock_write(mapping); hugetlb_dup_vma_private() and hugetlb_vm_op_open() are called outside i_mmap_rwsem lock while vma lock can be used in the same time. Fix this by deferring linking file vma until vma is fu... | CVSS3: 7.8 | 0% Низкий | больше 2 лет назад | |
BDU:2024-04584 Уязвимость функции dup_mmap() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации | CVSS3: 7.8 | 0% Низкий | больше 2 лет назад | |
ELSA-2024-6997 ELSA-2024-6997: kernel security update (IMPORTANT) | около 2 лет назад | |||
ROS-20241101-02 Множественные уязвимости kernel-lt | CVSS3: 7.8 | около 2 лет назад | ||
ALT-PU-2024-18371 ALT-PU-2024-18371: package `kernel-image-std-def` update to version 6.1.90-alt1 | CVSS3: 8.8 | больше 2 лет назад | ||
ALT-PU-2024-18473 ALT-PU-2024-18473: package `kernel-image-un-def` update to version 6.6.30-alt1 | CVSS3: 8.8 | больше 2 лет назад | ||
ALT-PU-2024-7242 ALT-PU-2024-7242: package `kernel-image-6.8` update to version 6.8.8-alt1 | CVSS3: 8.2 | больше 2 лет назад | ||
ALT-PU-2024-18214 ALT-PU-2024-18214: package `kernel-image-pine` update to version 6.6.30-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-17905 ALT-PU-2024-17905: package `kernel-image-un-def` update to version 6.1.90-alt1 | CVSS3: 9.1 | больше 1 года назад | ||
ALT-PU-2024-18118 ALT-PU-2024-18118: package `kernel-image-mp` update to version 6.8.8-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-7646 ALT-PU-2024-7646: package `kernel-image-rt` update to version 6.1.90-alt1.rt30 | CVSS3: 9.8 | больше 2 лет назад | ||
SUSE-SU-2024:2203-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:2135-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2024-13979 ALT-PU-2024-13979: package `kernel-image-rpi-un` update to version 6.6.56-alt1 | CVSS3: 7.8 | около 2 лет назад | ||
SUSE-SU-2024:2973-1 Security update for the Linux Kernel | около 2 лет назад |
Уязвимостей на страницу