Поиск уязвимостей
Количество 27
Количество 27
CVE-2025-22090
In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() If track_pfn_copy() fails, we already added the dst VMA to the maple tree. As fork() fails, we'll cleanup the maple tree, and stumble over the dst VMA for which we neither performed any reservation nor copied any page tables. Consequently untrack_pfn() will see VM_PAT and try obtaining the PAT information from the page table -- which fails because the page table was not copied. The easiest fix would be to simply clear the VM_PAT flag of the dst VMA if track_pfn_copy() fails. However, the whole thing is about "simply" clearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy() and performed a reservation, but copying the page tables fails, we'll simply clear the VM_PAT flag, not properly undoing the reservation ... which is also wrong. So let's fix it properly: set the VM_PAT flag only if the reservation succeeded (leaving it clear in...
CVE-2025-22090
In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() If track_pfn_copy() fails, we already added the dst VMA to the maple tree. As fork() fails, we'll cleanup the maple tree, and stumble over the dst VMA for which we neither performed any reservation nor copied any page tables. Consequently untrack_pfn() will see VM_PAT and try obtaining the PAT information from the page table -- which fails because the page table was not copied. The easiest fix would be to simply clear the VM_PAT flag of the dst VMA if track_pfn_copy() fails. However, the whole thing is about "simply" clearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy() and performed a reservation, but copying the page tables fails, we'll simply clear the VM_PAT flag, not properly undoing the reservation ... which is also wrong. So let's fix it properly: set the VM_PAT flag only if the reservation succeeded (leaving it clear in...
CVE-2025-22090
In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() If track_pfn_copy() fails, we already added the dst VMA to the maple tree. As fork() fails, we'll cleanup the maple tree, and stumble over the dst VMA for which we neither performed any reservation nor copied any page tables. Consequently untrack_pfn() will see VM_PAT and try obtaining the PAT information from the page table -- which fails because the page table was not copied. The easiest fix would be to simply clear the VM_PAT flag of the dst VMA if track_pfn_copy() fails. However, the whole thing is about "simply" clearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy() and performed a reservation, but copying the page tables fails, we'll simply clear the VM_PAT flag, not properly undoing the reservation ... which is also wrong. So let's fix it properly: set the VM_PAT flag only if the reservation succeeded (leaving it clear
CVE-2025-22090
x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()
CVE-2025-22090
In the Linux kernel, the following vulnerability has been resolved: x ...
GHSA-526j-rpwr-89fg
In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() If track_pfn_copy() fails, we already added the dst VMA to the maple tree. As fork() fails, we'll cleanup the maple tree, and stumble over the dst VMA for which we neither performed any reservation nor copied any page tables. Consequently untrack_pfn() will see VM_PAT and try obtaining the PAT information from the page table -- which fails because the page table was not copied. The easiest fix would be to simply clear the VM_PAT flag of the dst VMA if track_pfn_copy() fails. However, the whole thing is about "simply" clearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy() and performed a reservation, but copying the page tables fails, we'll simply clear the VM_PAT flag, not properly undoing the reservation ... which is also wrong. So let's fix it properly: set the VM_PAT flag only if the reservation succeeded (leaving it cle...
BDU:2026-01403
Уязвимость функции get_pat_info() модуля arch/x86/mm/pat/memtype.c платформы x86 ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260407-80-0002
Уязвимость kernel-lt
ROS-20260407-73-0002
Уязвимость kernel-lt
ALT-PU-2025-16453
ALT-PU-2025-16453: package `kernel-image-pine` update to version 6.12.23-alt2
SUSE-SU-2025:01707-1
Security update for the Linux Kernel
SUSE-SU-2025:01614-1
Security update for the Linux Kernel
SUSE-SU-2025:02996-1
Security update for the Linux Kernel
SUSE-SU-2025:02969-1
Security update for the Linux Kernel
SUSE-SU-2025:02997-1
Security update for the Linux Kernel
SUSE-SU-2025:03011-1
Security update for the Linux Kernel
ALT-PU-2025-5774
ALT-PU-2025-5774: package `kernel-image-6.12` update to version 6.12.24-alt1
SUSE-SU-2025:01951-1
Security update for the Linux Kernel
SUSE-SU-2025:01967-1
Security update for the Linux Kernel
SUSE-SU-2025:01964-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2025-22090 In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() If track_pfn_copy() fails, we already added the dst VMA to the maple tree. As fork() fails, we'll cleanup the maple tree, and stumble over the dst VMA for which we neither performed any reservation nor copied any page tables. Consequently untrack_pfn() will see VM_PAT and try obtaining the PAT information from the page table -- which fails because the page table was not copied. The easiest fix would be to simply clear the VM_PAT flag of the dst VMA if track_pfn_copy() fails. However, the whole thing is about "simply" clearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy() and performed a reservation, but copying the page tables fails, we'll simply clear the VM_PAT flag, not properly undoing the reservation ... which is also wrong. So let's fix it properly: set the VM_PAT flag only if the reservation succeeded (leaving it clear in... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2025-22090 In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() If track_pfn_copy() fails, we already added the dst VMA to the maple tree. As fork() fails, we'll cleanup the maple tree, and stumble over the dst VMA for which we neither performed any reservation nor copied any page tables. Consequently untrack_pfn() will see VM_PAT and try obtaining the PAT information from the page table -- which fails because the page table was not copied. The easiest fix would be to simply clear the VM_PAT flag of the dst VMA if track_pfn_copy() fails. However, the whole thing is about "simply" clearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy() and performed a reservation, but copying the page tables fails, we'll simply clear the VM_PAT flag, not properly undoing the reservation ... which is also wrong. So let's fix it properly: set the VM_PAT flag only if the reservation succeeded (leaving it clear in... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2025-22090 In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() If track_pfn_copy() fails, we already added the dst VMA to the maple tree. As fork() fails, we'll cleanup the maple tree, and stumble over the dst VMA for which we neither performed any reservation nor copied any page tables. Consequently untrack_pfn() will see VM_PAT and try obtaining the PAT information from the page table -- which fails because the page table was not copied. The easiest fix would be to simply clear the VM_PAT flag of the dst VMA if track_pfn_copy() fails. However, the whole thing is about "simply" clearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy() and performed a reservation, but copying the page tables fails, we'll simply clear the VM_PAT flag, not properly undoing the reservation ... which is also wrong. So let's fix it properly: set the VM_PAT flag only if the reservation succeeded (leaving it clear | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2025-22090 x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() | 0% Низкий | около 1 года назад | ||
CVE-2025-22090 In the Linux kernel, the following vulnerability has been resolved: x ... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
GHSA-526j-rpwr-89fg In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() If track_pfn_copy() fails, we already added the dst VMA to the maple tree. As fork() fails, we'll cleanup the maple tree, and stumble over the dst VMA for which we neither performed any reservation nor copied any page tables. Consequently untrack_pfn() will see VM_PAT and try obtaining the PAT information from the page table -- which fails because the page table was not copied. The easiest fix would be to simply clear the VM_PAT flag of the dst VMA if track_pfn_copy() fails. However, the whole thing is about "simply" clearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy() and performed a reservation, but copying the page tables fails, we'll simply clear the VM_PAT flag, not properly undoing the reservation ... which is also wrong. So let's fix it properly: set the VM_PAT flag only if the reservation succeeded (leaving it cle... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
BDU:2026-01403 Уязвимость функции get_pat_info() модуля arch/x86/mm/pat/memtype.c платформы x86 ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
ROS-20260407-80-0002 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 7 месяцев назад | |
ROS-20260407-73-0002 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 7 месяцев назад | |
ALT-PU-2025-16453 ALT-PU-2025-16453: package `kernel-image-pine` update to version 6.12.23-alt2 | CVSS3: 9.8 | больше 1 года назад | ||
SUSE-SU-2025:01707-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:01614-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:02996-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:02969-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:02997-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03011-1 Security update for the Linux Kernel | около 1 года назад | |||
ALT-PU-2025-5774 ALT-PU-2025-5774: package `kernel-image-6.12` update to version 6.12.24-alt1 | CVSS3: 9.8 | больше 1 года назад | ||
SUSE-SU-2025:01951-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:01967-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:01964-1 Security update for the Linux Kernel | больше 1 года назад |
Уязвимостей на страницу