Поиск уязвимостей
Количество 20
Количество 20
CVE-2024-35804
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Mark target gfn of emulated atomic instruction as dirty When emulating an atomic access on behalf of the guest, mark the target gfn dirty if the CMPXCHG by KVM is attempted and doesn't fault. This fixes a bug where KVM effectively corrupts guest memory during live migration by writing to guest memory without informing userspace that the page is dirty. Marking the page dirty got unintentionally dropped when KVM's emulated CMPXCHG was converted to do a user access. Before that, KVM explicitly mapped the guest page into kernel memory, and marked the page dirty during the unmap phase. Mark the page dirty even if the CMPXCHG fails, as the old data is written back on failure, i.e. the page is still written. The value written is guaranteed to be the same because the operation is atomic, but KVM's ABI is that all writes are dirty logged regardless of the value written. And more importantly, that's what KVM did...
CVE-2024-35804
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Mark target gfn of emulated atomic instruction as dirty When emulating an atomic access on behalf of the guest, mark the target gfn dirty if the CMPXCHG by KVM is attempted and doesn't fault. This fixes a bug where KVM effectively corrupts guest memory during live migration by writing to guest memory without informing userspace that the page is dirty. Marking the page dirty got unintentionally dropped when KVM's emulated CMPXCHG was converted to do a user access. Before that, KVM explicitly mapped the guest page into kernel memory, and marked the page dirty during the unmap phase. Mark the page dirty even if the CMPXCHG fails, as the old data is written back on failure, i.e. the page is still written. The value written is guaranteed to be the same because the operation is atomic, but KVM's ABI is that all writes are dirty logged regardless of the value written. And more importantly, that's what KVM did...
CVE-2024-35804
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Mark target gfn of emulated atomic instruction as dirty When emulating an atomic access on behalf of the guest, mark the target gfn dirty if the CMPXCHG by KVM is attempted and doesn't fault. This fixes a bug where KVM effectively corrupts guest memory during live migration by writing to guest memory without informing userspace that the page is dirty. Marking the page dirty got unintentionally dropped when KVM's emulated CMPXCHG was converted to do a user access. Before that, KVM explicitly mapped the guest page into kernel memory, and marked the page dirty during the unmap phase. Mark the page dirty even if the CMPXCHG fails, as the old data is written back on failure, i.e. the page is still written. The value written is guaranteed to be the same because the operation is atomic, but KVM's ABI is that all writes are dirty logged regardless of the value written. And more importantly, that's what KVM di
CVE-2024-35804
In the Linux kernel, the following vulnerability has been resolved: K ...
GHSA-x3cp-9cgr-m6gc
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Mark target gfn of emulated atomic instruction as dirty When emulating an atomic access on behalf of the guest, mark the target gfn dirty if the CMPXCHG by KVM is attempted and doesn't fault. This fixes a bug where KVM effectively corrupts guest memory during live migration by writing to guest memory without informing userspace that the page is dirty. Marking the page dirty got unintentionally dropped when KVM's emulated CMPXCHG was converted to do a user access. Before that, KVM explicitly mapped the guest page into kernel memory, and marked the page dirty during the unmap phase. Mark the page dirty even if the CMPXCHG fails, as the old data is written back on failure, i.e. the page is still written. The value written is guaranteed to be the same because the operation is atomic, but KVM's ABI is that all writes are dirty logged regardless of the value written. And more importantly, that's what KVM...
BDU:2024-09772
Уязвимость компонента x86 ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20241106-01
Множественные уязвимости kernel-lt
ALT-PU-2024-18366
ALT-PU-2024-18366: package `kernel-image-std-def` update to version 6.1.84-alt1
ALT-PU-2024-18059
ALT-PU-2024-18059: package `kernel-image-un-def` update to version 6.1.84-alt1
ALT-PU-2024-18470
ALT-PU-2024-18470: package `kernel-image-un-def` update to version 6.6.24-alt1
ALT-PU-2024-18212
ALT-PU-2024-18212: package `kernel-image-pine` update to version 6.6.27-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
SUSE-SU-2024:2019-1
Security update for the Linux Kernel
SUSE-SU-2024:2190-1
Security update for the Linux Kernel
ALT-PU-2024-18117
ALT-PU-2024-18117: package `kernel-image-mp` update to version 6.7.12-alt1
SUSE-SU-2024:2008-1
Security update for the Linux Kernel
SUSE-SU-2024:2973-1
Security update for the Linux Kernel
ALT-PU-2024-14046
ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-35804 In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Mark target gfn of emulated atomic instruction as dirty When emulating an atomic access on behalf of the guest, mark the target gfn dirty if the CMPXCHG by KVM is attempted and doesn't fault. This fixes a bug where KVM effectively corrupts guest memory during live migration by writing to guest memory without informing userspace that the page is dirty. Marking the page dirty got unintentionally dropped when KVM's emulated CMPXCHG was converted to do a user access. Before that, KVM explicitly mapped the guest page into kernel memory, and marked the page dirty during the unmap phase. Mark the page dirty even if the CMPXCHG fails, as the old data is written back on failure, i.e. the page is still written. The value written is guaranteed to be the same because the operation is atomic, but KVM's ABI is that all writes are dirty logged regardless of the value written. And more importantly, that's what KVM did... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-35804 In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Mark target gfn of emulated atomic instruction as dirty When emulating an atomic access on behalf of the guest, mark the target gfn dirty if the CMPXCHG by KVM is attempted and doesn't fault. This fixes a bug where KVM effectively corrupts guest memory during live migration by writing to guest memory without informing userspace that the page is dirty. Marking the page dirty got unintentionally dropped when KVM's emulated CMPXCHG was converted to do a user access. Before that, KVM explicitly mapped the guest page into kernel memory, and marked the page dirty during the unmap phase. Mark the page dirty even if the CMPXCHG fails, as the old data is written back on failure, i.e. the page is still written. The value written is guaranteed to be the same because the operation is atomic, but KVM's ABI is that all writes are dirty logged regardless of the value written. And more importantly, that's what KVM did... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-35804 In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Mark target gfn of emulated atomic instruction as dirty When emulating an atomic access on behalf of the guest, mark the target gfn dirty if the CMPXCHG by KVM is attempted and doesn't fault. This fixes a bug where KVM effectively corrupts guest memory during live migration by writing to guest memory without informing userspace that the page is dirty. Marking the page dirty got unintentionally dropped when KVM's emulated CMPXCHG was converted to do a user access. Before that, KVM explicitly mapped the guest page into kernel memory, and marked the page dirty during the unmap phase. Mark the page dirty even if the CMPXCHG fails, as the old data is written back on failure, i.e. the page is still written. The value written is guaranteed to be the same because the operation is atomic, but KVM's ABI is that all writes are dirty logged regardless of the value written. And more importantly, that's what KVM di | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-35804 In the Linux kernel, the following vulnerability has been resolved: K ... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
GHSA-x3cp-9cgr-m6gc In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Mark target gfn of emulated atomic instruction as dirty When emulating an atomic access on behalf of the guest, mark the target gfn dirty if the CMPXCHG by KVM is attempted and doesn't fault. This fixes a bug where KVM effectively corrupts guest memory during live migration by writing to guest memory without informing userspace that the page is dirty. Marking the page dirty got unintentionally dropped when KVM's emulated CMPXCHG was converted to do a user access. Before that, KVM explicitly mapped the guest page into kernel memory, and marked the page dirty during the unmap phase. Mark the page dirty even if the CMPXCHG fails, as the old data is written back on failure, i.e. the page is still written. The value written is guaranteed to be the same because the operation is atomic, but KVM's ABI is that all writes are dirty logged regardless of the value written. And more importantly, that's what KVM... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
BDU:2024-09772 Уязвимость компонента x86 ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
ROS-20241106-01 Множественные уязвимости kernel-lt | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2024-18366 ALT-PU-2024-18366: package `kernel-image-std-def` update to version 6.1.84-alt1 | CVSS3: 8.8 | больше 2 лет назад | ||
ALT-PU-2024-18059 ALT-PU-2024-18059: package `kernel-image-un-def` update to version 6.1.84-alt1 | CVSS3: 8.8 | больше 2 лет назад | ||
ALT-PU-2024-18470 ALT-PU-2024-18470: package `kernel-image-un-def` update to version 6.6.24-alt1 | CVSS3: 8.8 | больше 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-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 лет назад | |||
SUSE-SU-2024:2019-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:2190-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2024-18117 ALT-PU-2024-18117: package `kernel-image-mp` update to version 6.7.12-alt1 | CVSS3: 9.1 | больше 2 лет назад | ||
SUSE-SU-2024:2008-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:2973-1 Security update for the Linux Kernel | около 2 лет назад | |||
ALT-PU-2024-14046 ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1 | CVSS3: 9.8 | почти 2 года назад |
Уязвимостей на страницу