Поиск уязвимостей
Количество 30
Количество 30
CVE-2024-35877
In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: fix VM_PAT handling in COW mappings PAT handling won't do the right thing in COW mappings: the first PTE (or, in fact, all PTEs) can be replaced during write faults to point at anon folios. Reliably recovering the correct PFN and cachemode using follow_phys() from PTEs will not work in COW mappings. Using follow_phys(), we might just get the address+protection of the anon folio (which is very wrong), or fail on swap/nonswap entries, failing follow_phys() and triggering a WARN_ON_ONCE() in untrack_pfn() and track_pfn_copy(), not properly calling free_pfn_range(). In free_pfn_range(), we either wouldn't call memtype_free() or would call it with the wrong range, possibly leaking memory. To fix that, let's update follow_phys() to refuse returning anon folios, and fallback to using the stored PFN inside vma->vm_pgoff for COW mappings if we run into that. We will now properly handle untrack_pfn() with COW map...
CVE-2024-35877
In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: fix VM_PAT handling in COW mappings PAT handling won't do the right thing in COW mappings: the first PTE (or, in fact, all PTEs) can be replaced during write faults to point at anon folios. Reliably recovering the correct PFN and cachemode using follow_phys() from PTEs will not work in COW mappings. Using follow_phys(), we might just get the address+protection of the anon folio (which is very wrong), or fail on swap/nonswap entries, failing follow_phys() and triggering a WARN_ON_ONCE() in untrack_pfn() and track_pfn_copy(), not properly calling free_pfn_range(). In free_pfn_range(), we either wouldn't call memtype_free() or would call it with the wrong range, possibly leaking memory. To fix that, let's update follow_phys() to refuse returning anon folios, and fallback to using the stored PFN inside vma->vm_pgoff for COW mappings if we run into that. We will now properly handle untrack_pfn() with COW map...
CVE-2024-35877
In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: fix VM_PAT handling in COW mappings PAT handling won't do the right thing in COW mappings: the first PTE (or, in fact, all PTEs) can be replaced during write faults to point at anon folios. Reliably recovering the correct PFN and cachemode using follow_phys() from PTEs will not work in COW mappings. Using follow_phys(), we might just get the address+protection of the anon folio (which is very wrong), or fail on swap/nonswap entries, failing follow_phys() and triggering a WARN_ON_ONCE() in untrack_pfn() and track_pfn_copy(), not properly calling free_pfn_range(). In free_pfn_range(), we either wouldn't call memtype_free() or would call it with the wrong range, possibly leaking memory. To fix that, let's update follow_phys() to refuse returning anon folios, and fallback to using the stored PFN inside vma->vm_pgoff for COW mappings if we run into that. We will now properly handle untrack_pfn() with COW
CVE-2024-35877
In the Linux kernel, the following vulnerability has been resolved: x ...
GHSA-mgpj-gvmw-xq4j
In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: fix VM_PAT handling in COW mappings PAT handling won't do the right thing in COW mappings: the first PTE (or, in fact, all PTEs) can be replaced during write faults to point at anon folios. Reliably recovering the correct PFN and cachemode using follow_phys() from PTEs will not work in COW mappings. Using follow_phys(), we might just get the address+protection of the anon folio (which is very wrong), or fail on swap/nonswap entries, failing follow_phys() and triggering a WARN_ON_ONCE() in untrack_pfn() and track_pfn_copy(), not properly calling free_pfn_range(). In free_pfn_range(), we either wouldn't call memtype_free() or would call it with the wrong range, possibly leaking memory. To fix that, let's update follow_phys() to refuse returning anon folios, and fallback to using the stored PFN inside vma->vm_pgoff for COW mappings if we run into that. We will now properly handle untrack_pfn() with C...
BDU:2024-10065
Уязвимость компонентов x86/mm/pat ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ELSA-2024-12700
ELSA-2024-12700: Unbreakable Enterprise kernel security update (IMPORTANT)
ROS-20241118-01
Множественные уязвимости kernel-lt
ALT-PU-2024-18367
ALT-PU-2024-18367: package `kernel-image-std-def` update to version 6.1.85-alt1
ALT-PU-2024-18060
ALT-PU-2024-18060: package `kernel-image-un-def` update to version 6.1.85-alt1
ALT-PU-2024-18471
ALT-PU-2024-18471: package `kernel-image-un-def` update to version 6.6.26-alt1
ALT-PU-2024-18144
ALT-PU-2024-18144: package `kernel-image-6.8` update to version 6.8.5-alt1
ELSA-2024-7000
ELSA-2024-7000: kernel security update (IMPORTANT)
RLSA-2024:7000
Important: kernel security update
SUSE-SU-2024:1979-1
Security update for the Linux Kernel
SUSE-SU-2024:2184-1
Security update for the Linux Kernel
SUSE-SU-2024:1983-1
Security update for the Linux Kernel
ALT-PU-2024-18077
ALT-PU-2024-18077: package `kernel-image-rt` update to version 5.10.215-alt1.rt107
ALT-PU-2024-18212
ALT-PU-2024-18212: package `kernel-image-pine` update to version 6.6.27-alt1
ALT-PU-2024-18118
ALT-PU-2024-18118: package `kernel-image-mp` update to version 6.8.8-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-35877 In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: fix VM_PAT handling in COW mappings PAT handling won't do the right thing in COW mappings: the first PTE (or, in fact, all PTEs) can be replaced during write faults to point at anon folios. Reliably recovering the correct PFN and cachemode using follow_phys() from PTEs will not work in COW mappings. Using follow_phys(), we might just get the address+protection of the anon folio (which is very wrong), or fail on swap/nonswap entries, failing follow_phys() and triggering a WARN_ON_ONCE() in untrack_pfn() and track_pfn_copy(), not properly calling free_pfn_range(). In free_pfn_range(), we either wouldn't call memtype_free() or would call it with the wrong range, possibly leaking memory. To fix that, let's update follow_phys() to refuse returning anon folios, and fallback to using the stored PFN inside vma->vm_pgoff for COW mappings if we run into that. We will now properly handle untrack_pfn() with COW map... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-35877 In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: fix VM_PAT handling in COW mappings PAT handling won't do the right thing in COW mappings: the first PTE (or, in fact, all PTEs) can be replaced during write faults to point at anon folios. Reliably recovering the correct PFN and cachemode using follow_phys() from PTEs will not work in COW mappings. Using follow_phys(), we might just get the address+protection of the anon folio (which is very wrong), or fail on swap/nonswap entries, failing follow_phys() and triggering a WARN_ON_ONCE() in untrack_pfn() and track_pfn_copy(), not properly calling free_pfn_range(). In free_pfn_range(), we either wouldn't call memtype_free() or would call it with the wrong range, possibly leaking memory. To fix that, let's update follow_phys() to refuse returning anon folios, and fallback to using the stored PFN inside vma->vm_pgoff for COW mappings if we run into that. We will now properly handle untrack_pfn() with COW map... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-35877 In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: fix VM_PAT handling in COW mappings PAT handling won't do the right thing in COW mappings: the first PTE (or, in fact, all PTEs) can be replaced during write faults to point at anon folios. Reliably recovering the correct PFN and cachemode using follow_phys() from PTEs will not work in COW mappings. Using follow_phys(), we might just get the address+protection of the anon folio (which is very wrong), or fail on swap/nonswap entries, failing follow_phys() and triggering a WARN_ON_ONCE() in untrack_pfn() and track_pfn_copy(), not properly calling free_pfn_range(). In free_pfn_range(), we either wouldn't call memtype_free() or would call it with the wrong range, possibly leaking memory. To fix that, let's update follow_phys() to refuse returning anon folios, and fallback to using the stored PFN inside vma->vm_pgoff for COW mappings if we run into that. We will now properly handle untrack_pfn() with COW | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-35877 In the Linux kernel, the following vulnerability has been resolved: x ... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
GHSA-mgpj-gvmw-xq4j In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: fix VM_PAT handling in COW mappings PAT handling won't do the right thing in COW mappings: the first PTE (or, in fact, all PTEs) can be replaced during write faults to point at anon folios. Reliably recovering the correct PFN and cachemode using follow_phys() from PTEs will not work in COW mappings. Using follow_phys(), we might just get the address+protection of the anon folio (which is very wrong), or fail on swap/nonswap entries, failing follow_phys() and triggering a WARN_ON_ONCE() in untrack_pfn() and track_pfn_copy(), not properly calling free_pfn_range(). In free_pfn_range(), we either wouldn't call memtype_free() or would call it with the wrong range, possibly leaking memory. To fix that, let's update follow_phys() to refuse returning anon folios, and fallback to using the stored PFN inside vma->vm_pgoff for COW mappings if we run into that. We will now properly handle untrack_pfn() with C... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
BDU:2024-10065 Уязвимость компонентов x86/mm/pat ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
ELSA-2024-12700 ELSA-2024-12700: Unbreakable Enterprise kernel security update (IMPORTANT) | около 2 лет назад | |||
ROS-20241118-01 Множественные уязвимости kernel-lt | CVSS3: 8.8 | почти 2 года назад | ||
ALT-PU-2024-18367 ALT-PU-2024-18367: package `kernel-image-std-def` update to version 6.1.85-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-18060 ALT-PU-2024-18060: package `kernel-image-un-def` update to version 6.1.85-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-18471 ALT-PU-2024-18471: package `kernel-image-un-def` update to version 6.6.26-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-18144 ALT-PU-2024-18144: package `kernel-image-6.8` update to version 6.8.5-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ELSA-2024-7000 ELSA-2024-7000: kernel security update (IMPORTANT) | около 2 лет назад | |||
RLSA-2024:7000 Important: kernel security update | больше 1 года назад | |||
SUSE-SU-2024:1979-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:2184-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:1983-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2024-18077 ALT-PU-2024-18077: package `kernel-image-rt` update to version 5.10.215-alt1.rt107 | CVSS3: 9.1 | больше 2 лет назад | ||
ALT-PU-2024-18212 ALT-PU-2024-18212: package `kernel-image-pine` update to version 6.6.27-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-18118 ALT-PU-2024-18118: package `kernel-image-mp` update to version 6.8.8-alt1 | CVSS3: 9.8 | больше 2 лет назад |
Уязвимостей на страницу