Поиск уязвимостей
Количество 15
Количество 15
CVE-2021-47214
In the Linux kernel, the following vulnerability has been resolved: hugetlb, userfaultfd: fix reservation restore on userfaultfd error Currently in the is_continue case in hugetlb_mcopy_atomic_pte(), if we bail out using "goto out_release_unlock;" in the cases where idx >= size, or !huge_pte_none(), the code will detect that new_pagecache_page == false, and so call restore_reserve_on_error(). In this case I see restore_reserve_on_error() delete the reservation, and the following call to remove_inode_hugepages() will increment h->resv_hugepages causing a 100% reproducible leak. We should treat the is_continue case similar to adding a page into the pagecache and set new_pagecache_page to true, to indicate that there is no reservation to restore on the error path, and we need not call restore_reserve_on_error(). Rename new_pagecache_page to page_in_pagecache to make that clear.
CVE-2021-47214
In the Linux kernel, the following vulnerability has been resolved: hugetlb, userfaultfd: fix reservation restore on userfaultfd error Currently in the is_continue case in hugetlb_mcopy_atomic_pte(), if we bail out using "goto out_release_unlock;" in the cases where idx >= size, or !huge_pte_none(), the code will detect that new_pagecache_page == false, and so call restore_reserve_on_error(). In this case I see restore_reserve_on_error() delete the reservation, and the following call to remove_inode_hugepages() will increment h->resv_hugepages causing a 100% reproducible leak. We should treat the is_continue case similar to adding a page into the pagecache and set new_pagecache_page to true, to indicate that there is no reservation to restore on the error path, and we need not call restore_reserve_on_error(). Rename new_pagecache_page to page_in_pagecache to make that clear.
CVE-2021-47214
In the Linux kernel, the following vulnerability has been resolved: hugetlb, userfaultfd: fix reservation restore on userfaultfd error Currently in the is_continue case in hugetlb_mcopy_atomic_pte(), if we bail out using "goto out_release_unlock;" in the cases where idx >= size, or !huge_pte_none(), the code will detect that new_pagecache_page == false, and so call restore_reserve_on_error(). In this case I see restore_reserve_on_error() delete the reservation, and the following call to remove_inode_hugepages() will increment h->resv_hugepages causing a 100% reproducible leak. We should treat the is_continue case similar to adding a page into the pagecache and set new_pagecache_page to true, to indicate that there is no reservation to restore on the error path, and we need not call restore_reserve_on_error(). Rename new_pagecache_page to page_in_pagecache to make that clear.
CVE-2021-47214
In the Linux kernel, the following vulnerability has been resolved: h ...
GHSA-rr47-vpr9-84rm
In the Linux kernel, the following vulnerability has been resolved: hugetlb, userfaultfd: fix reservation restore on userfaultfd error Currently in the is_continue case in hugetlb_mcopy_atomic_pte(), if we bail out using "goto out_release_unlock;" in the cases where idx >= size, or !huge_pte_none(), the code will detect that new_pagecache_page == false, and so call restore_reserve_on_error(). In this case I see restore_reserve_on_error() delete the reservation, and the following call to remove_inode_hugepages() will increment h->resv_hugepages causing a 100% reproducible leak. We should treat the is_continue case similar to adding a page into the pagecache and set new_pagecache_page to true, to indicate that there is no reservation to restore on the error path, and we need not call restore_reserve_on_error(). Rename new_pagecache_page to page_in_pagecache to make that clear.
BDU:2024-09137
Уязвимость компонента hugetlb ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ALT-PU-2021-2749
ALT-PU-2021-2749: package `kernel-image-un-def` update to version 5.13.14-alt1
ALT-PU-2021-2723
ALT-PU-2021-2723: package `kernel-image-un-def` update to version 5.13.14-alt1
ROS-20241025-02
Множественные уязвимости kernel-lt
ALT-PU-2021-3358
ALT-PU-2021-3358: package `kernel-image-un-def` update to version 5.15.5-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
ALT-PU-2021-4935
ALT-PU-2021-4935: package `kernel-image-mp` update to version 5.15.8-alt1
ALT-PU-2021-3660
ALT-PU-2021-3660: package `kernel-image-un-def` update to version 5.15.11-alt2
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2021-47214 In the Linux kernel, the following vulnerability has been resolved: hugetlb, userfaultfd: fix reservation restore on userfaultfd error Currently in the is_continue case in hugetlb_mcopy_atomic_pte(), if we bail out using "goto out_release_unlock;" in the cases where idx >= size, or !huge_pte_none(), the code will detect that new_pagecache_page == false, and so call restore_reserve_on_error(). In this case I see restore_reserve_on_error() delete the reservation, and the following call to remove_inode_hugepages() will increment h->resv_hugepages causing a 100% reproducible leak. We should treat the is_continue case similar to adding a page into the pagecache and set new_pagecache_page to true, to indicate that there is no reservation to restore on the error path, and we need not call restore_reserve_on_error(). Rename new_pagecache_page to page_in_pagecache to make that clear. | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2021-47214 In the Linux kernel, the following vulnerability has been resolved: hugetlb, userfaultfd: fix reservation restore on userfaultfd error Currently in the is_continue case in hugetlb_mcopy_atomic_pte(), if we bail out using "goto out_release_unlock;" in the cases where idx >= size, or !huge_pte_none(), the code will detect that new_pagecache_page == false, and so call restore_reserve_on_error(). In this case I see restore_reserve_on_error() delete the reservation, and the following call to remove_inode_hugepages() will increment h->resv_hugepages causing a 100% reproducible leak. We should treat the is_continue case similar to adding a page into the pagecache and set new_pagecache_page to true, to indicate that there is no reservation to restore on the error path, and we need not call restore_reserve_on_error(). Rename new_pagecache_page to page_in_pagecache to make that clear. | CVSS3: 6.1 | 0% Низкий | больше 2 лет назад | |
CVE-2021-47214 In the Linux kernel, the following vulnerability has been resolved: hugetlb, userfaultfd: fix reservation restore on userfaultfd error Currently in the is_continue case in hugetlb_mcopy_atomic_pte(), if we bail out using "goto out_release_unlock;" in the cases where idx >= size, or !huge_pte_none(), the code will detect that new_pagecache_page == false, and so call restore_reserve_on_error(). In this case I see restore_reserve_on_error() delete the reservation, and the following call to remove_inode_hugepages() will increment h->resv_hugepages causing a 100% reproducible leak. We should treat the is_continue case similar to adding a page into the pagecache and set new_pagecache_page to true, to indicate that there is no reservation to restore on the error path, and we need not call restore_reserve_on_error(). Rename new_pagecache_page to page_in_pagecache to make that clear. | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2021-47214 In the Linux kernel, the following vulnerability has been resolved: h ... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
GHSA-rr47-vpr9-84rm In the Linux kernel, the following vulnerability has been resolved: hugetlb, userfaultfd: fix reservation restore on userfaultfd error Currently in the is_continue case in hugetlb_mcopy_atomic_pte(), if we bail out using "goto out_release_unlock;" in the cases where idx >= size, or !huge_pte_none(), the code will detect that new_pagecache_page == false, and so call restore_reserve_on_error(). In this case I see restore_reserve_on_error() delete the reservation, and the following call to remove_inode_hugepages() will increment h->resv_hugepages causing a 100% reproducible leak. We should treat the is_continue case similar to adding a page into the pagecache and set new_pagecache_page to true, to indicate that there is no reservation to restore on the error path, and we need not call restore_reserve_on_error(). Rename new_pagecache_page to page_in_pagecache to make that clear. | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
BDU:2024-09137 Уязвимость компонента hugetlb ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | почти 5 лет назад | |
ALT-PU-2021-2749 ALT-PU-2021-2749: package `kernel-image-un-def` update to version 5.13.14-alt1 | CVSS3: 7.8 | около 5 лет назад | ||
ALT-PU-2021-2723 ALT-PU-2021-2723: package `kernel-image-un-def` update to version 5.13.14-alt1 | CVSS3: 7.8 | около 5 лет назад | ||
ROS-20241025-02 Множественные уязвимости kernel-lt | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2021-3358 ALT-PU-2021-3358: package `kernel-image-un-def` update to version 5.15.5-alt1 | CVSS3: 9.3 | почти 5 лет назад | ||
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 лет назад | |||
ALT-PU-2021-4935 ALT-PU-2021-4935: package `kernel-image-mp` update to version 5.15.8-alt1 | CVSS3: 9.8 | почти 5 лет назад | ||
ALT-PU-2021-3660 ALT-PU-2021-3660: package `kernel-image-un-def` update to version 5.15.11-alt2 | CVSS3: 9.8 | почти 5 лет назад |
Уязвимостей на страницу