Количество 24
Количество 24
CVE-2026-23198
In the Linux kernel, the following vulnerability has been resolved: KVM: Don't clobber irqfd routing type when deassigning irqfd When deassigning a KVM_IRQFD, don't clobber the irqfd's copy of the IRQ's routing entry as doing so breaks kvm_arch_irq_bypass_del_producer() on x86 and arm64, which explicitly look for KVM_IRQ_ROUTING_MSI. Instead, to handle a concurrent routing update, verify that the irqfd is still active before consuming the routing information. As evidenced by the x86 and arm64 bugs, and another bug in kvm_arch_update_irqfd_routing() (see below), clobbering the entry type without notifying arch code is surprising and error prone. As a bonus, checking that the irqfd is active provides a convenient location for documenting _why_ KVM must not consume the routing entry for an irqfd that is in the process of being deassigned: once the irqfd is deleted from the list (which happens *before* the eventfd is detached), it will no longer receive updates via kvm_irq_routing_upd...
CVE-2026-23198
In the Linux kernel, the following vulnerability has been resolved: KVM: Don't clobber irqfd routing type when deassigning irqfd When deassigning a KVM_IRQFD, don't clobber the irqfd's copy of the IRQ's routing entry as doing so breaks kvm_arch_irq_bypass_del_producer() on x86 and arm64, which explicitly look for KVM_IRQ_ROUTING_MSI. Instead, to handle a concurrent routing update, verify that the irqfd is still active before consuming the routing information. As evidenced by the x86 and arm64 bugs, and another bug in kvm_arch_update_irqfd_routing() (see below), clobbering the entry type without notifying arch code is surprising and error prone. As a bonus, checking that the irqfd is active provides a convenient location for documenting _why_ KVM must not consume the routing entry for an irqfd that is in the process of being deassigned: once the irqfd is deleted from the list (which happens *before* the eventfd is detached), it will no longer receive updates via kvm_irq_routing_upd...
CVE-2026-23198
In the Linux kernel, the following vulnerability has been resolved: KVM: Don't clobber irqfd routing type when deassigning irqfd When deassigning a KVM_IRQFD, don't clobber the irqfd's copy of the IRQ's routing entry as doing so breaks kvm_arch_irq_bypass_del_producer() on x86 and arm64, which explicitly look for KVM_IRQ_ROUTING_MSI. Instead, to handle a concurrent routing update, verify that the irqfd is still active before consuming the routing information. As evidenced by the x86 and arm64 bugs, and another bug in kvm_arch_update_irqfd_routing() (see below), clobbering the entry type without notifying arch code is surprising and error prone. As a bonus, checking that the irqfd is active provides a convenient location for documenting _why_ KVM must not consume the routing entry for an irqfd that is in the process of being deassigned: once the irqfd is deleted from the list (which happens *before* the eventfd is detached), it will no longer receive updates via kvm_irq_routing_upd
CVE-2026-23198
In the Linux kernel, the following vulnerability has been resolved: K ...
GHSA-68jg-6v9h-662h
In the Linux kernel, the following vulnerability has been resolved: KVM: Don't clobber irqfd routing type when deassigning irqfd When deassigning a KVM_IRQFD, don't clobber the irqfd's copy of the IRQ's routing entry as doing so breaks kvm_arch_irq_bypass_del_producer() on x86 and arm64, which explicitly look for KVM_IRQ_ROUTING_MSI. Instead, to handle a concurrent routing update, verify that the irqfd is still active before consuming the routing information. As evidenced by the x86 and arm64 bugs, and another bug in kvm_arch_update_irqfd_routing() (see below), clobbering the entry type without notifying arch code is surprising and error prone. As a bonus, checking that the irqfd is active provides a convenient location for documenting _why_ KVM must not consume the routing entry for an irqfd that is in the process of being deassigned: once the irqfd is deleted from the list (which happens *before* the eventfd is detached), it will no longer receive updates via kvm_irq_routing_...
BDU:2026-11605
Уязвимость компонента virt/kvm/eventfd.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260918-80-0069
Уязвимость kernel-lt
ROS-20260918-73-0064
Уязвимость kernel-lt
SUSE-SU-2026:1078-1
Security update for the Linux Kernel
ALT-PU-2026-3821
ALT-PU-2026-3821: package `kernel-image-rt` update to version 5.10.250-alt1.rt145
ALT-PU-2026-2587
ALT-PU-2026-2587: package `kernel-image-std-def` update to version 5.10.250-alt1
ELSA-2026-50160
ELSA-2026-50160: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2026:0962-1
Security update for the Linux Kernel
SUSE-SU-2026:1081-1
Security update for the Linux Kernel
ALT-PU-2026-5135
ALT-PU-2026-5135: package `kernel-image-6.18` update to version 6.18.20-alt1
openSUSE-SU-2026:20416-1
Security update for the Linux Kernel
ALT-PU-2026-3309
ALT-PU-2026-3309: package `kernel-image-rt` update to version 6.12.74-alt1
ALT-PU-2026-3243
ALT-PU-2026-3243: package `kernel-image-6.12` update to version 6.12.74-alt1
ALT-PU-2026-3750
ALT-PU-2026-3750: package `kernel-image-un-def` update to version 6.1.163-alt1
ALT-PU-2026-4046
ALT-PU-2026-4046: package `kernel-image-pine` update to version 6.18.13-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-23198 In the Linux kernel, the following vulnerability has been resolved: KVM: Don't clobber irqfd routing type when deassigning irqfd When deassigning a KVM_IRQFD, don't clobber the irqfd's copy of the IRQ's routing entry as doing so breaks kvm_arch_irq_bypass_del_producer() on x86 and arm64, which explicitly look for KVM_IRQ_ROUTING_MSI. Instead, to handle a concurrent routing update, verify that the irqfd is still active before consuming the routing information. As evidenced by the x86 and arm64 bugs, and another bug in kvm_arch_update_irqfd_routing() (see below), clobbering the entry type without notifying arch code is surprising and error prone. As a bonus, checking that the irqfd is active provides a convenient location for documenting _why_ KVM must not consume the routing entry for an irqfd that is in the process of being deassigned: once the irqfd is deleted from the list (which happens *before* the eventfd is detached), it will no longer receive updates via kvm_irq_routing_upd... | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад | |
CVE-2026-23198 In the Linux kernel, the following vulnerability has been resolved: KVM: Don't clobber irqfd routing type when deassigning irqfd When deassigning a KVM_IRQFD, don't clobber the irqfd's copy of the IRQ's routing entry as doing so breaks kvm_arch_irq_bypass_del_producer() on x86 and arm64, which explicitly look for KVM_IRQ_ROUTING_MSI. Instead, to handle a concurrent routing update, verify that the irqfd is still active before consuming the routing information. As evidenced by the x86 and arm64 bugs, and another bug in kvm_arch_update_irqfd_routing() (see below), clobbering the entry type without notifying arch code is surprising and error prone. As a bonus, checking that the irqfd is active provides a convenient location for documenting _why_ KVM must not consume the routing entry for an irqfd that is in the process of being deassigned: once the irqfd is deleted from the list (which happens *before* the eventfd is detached), it will no longer receive updates via kvm_irq_routing_upd... | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад | |
CVE-2026-23198 In the Linux kernel, the following vulnerability has been resolved: KVM: Don't clobber irqfd routing type when deassigning irqfd When deassigning a KVM_IRQFD, don't clobber the irqfd's copy of the IRQ's routing entry as doing so breaks kvm_arch_irq_bypass_del_producer() on x86 and arm64, which explicitly look for KVM_IRQ_ROUTING_MSI. Instead, to handle a concurrent routing update, verify that the irqfd is still active before consuming the routing information. As evidenced by the x86 and arm64 bugs, and another bug in kvm_arch_update_irqfd_routing() (see below), clobbering the entry type without notifying arch code is surprising and error prone. As a bonus, checking that the irqfd is active provides a convenient location for documenting _why_ KVM must not consume the routing entry for an irqfd that is in the process of being deassigned: once the irqfd is deleted from the list (which happens *before* the eventfd is detached), it will no longer receive updates via kvm_irq_routing_upd | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад | |
CVE-2026-23198 In the Linux kernel, the following vulnerability has been resolved: K ... | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад | |
GHSA-68jg-6v9h-662h In the Linux kernel, the following vulnerability has been resolved: KVM: Don't clobber irqfd routing type when deassigning irqfd When deassigning a KVM_IRQFD, don't clobber the irqfd's copy of the IRQ's routing entry as doing so breaks kvm_arch_irq_bypass_del_producer() on x86 and arm64, which explicitly look for KVM_IRQ_ROUTING_MSI. Instead, to handle a concurrent routing update, verify that the irqfd is still active before consuming the routing information. As evidenced by the x86 and arm64 bugs, and another bug in kvm_arch_update_irqfd_routing() (see below), clobbering the entry type without notifying arch code is surprising and error prone. As a bonus, checking that the irqfd is active provides a convenient location for documenting _why_ KVM must not consume the routing entry for an irqfd that is in the process of being deassigned: once the irqfd is deleted from the list (which happens *before* the eventfd is detached), it will no longer receive updates via kvm_irq_routing_... | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад | |
BDU:2026-11605 Уязвимость компонента virt/kvm/eventfd.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 7.8 | 0% Низкий | 10 месяцев назад | |
ROS-20260918-80-0069 Уязвимость kernel-lt | CVSS3: 7.8 | 0% Низкий | около 1 месяца назад | |
ROS-20260918-73-0064 Уязвимость kernel-lt | CVSS3: 7.8 | 0% Низкий | около 1 месяца назад | |
SUSE-SU-2026:1078-1 Security update for the Linux Kernel | 7 месяцев назад | |||
ALT-PU-2026-3821 ALT-PU-2026-3821: package `kernel-image-rt` update to version 5.10.250-alt1.rt145 | CVSS3: 9.8 | 8 месяцев назад | ||
ALT-PU-2026-2587 ALT-PU-2026-2587: package `kernel-image-std-def` update to version 5.10.250-alt1 | CVSS3: 9.8 | 8 месяцев назад | ||
ELSA-2026-50160 ELSA-2026-50160: Unbreakable Enterprise kernel security update (IMPORTANT) | 7 месяцев назад | |||
SUSE-SU-2026:0962-1 Security update for the Linux Kernel | 7 месяцев назад | |||
SUSE-SU-2026:1081-1 Security update for the Linux Kernel | 7 месяцев назад | |||
ALT-PU-2026-5135 ALT-PU-2026-5135: package `kernel-image-6.18` update to version 6.18.20-alt1 | CVSS3: 9.8 | 7 месяцев назад | ||
openSUSE-SU-2026:20416-1 Security update for the Linux Kernel | 7 месяцев назад | |||
ALT-PU-2026-3309 ALT-PU-2026-3309: package `kernel-image-rt` update to version 6.12.74-alt1 | CVSS3: 9.8 | 8 месяцев назад | ||
ALT-PU-2026-3243 ALT-PU-2026-3243: package `kernel-image-6.12` update to version 6.12.74-alt1 | CVSS3: 9.8 | 8 месяцев назад | ||
ALT-PU-2026-3750 ALT-PU-2026-3750: package `kernel-image-un-def` update to version 6.1.163-alt1 | CVSS3: 9.8 | 8 месяцев назад | ||
ALT-PU-2026-4046 ALT-PU-2026-4046: package `kernel-image-pine` update to version 6.18.13-alt1 | CVSS3: 9.8 | 8 месяцев назад |
Уязвимостей на страницу