Поиск уязвимостей
Количество 26
Количество 26
CVE-2026-23085
In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Avoid truncating memory addresses On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem allocations to be backed by addresses physical memory above the 32-bit address limit, as found while experimenting with larger VMSPLIT configurations. This caused the qemu virt model to crash in the GICv3 driver, which allocates the 'itt' object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses for ZONE_NORMAL, and the ITS driver stores the physical address in a 32-bit 'unsigned long' variable. Change the itt_addr variable to the correct phys_addr_t type instead, along with all other variables in this driver that hold a physical address. The gicv5 driver correctly uses u64 variables, while all other irqchip drivers don't call virt_to_phys or similar interfaces. It's expected that other device drivers...
CVE-2026-23085
In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Avoid truncating memory addresses On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem allocations to be backed by addresses physical memory above the 32-bit address limit, as found while experimenting with larger VMSPLIT configurations. This caused the qemu virt model to crash in the GICv3 driver, which allocates the 'itt' object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses for ZONE_NORMAL, and the ITS driver stores the physical address in a 32-bit 'unsigned long' variable. Change the itt_addr variable to the correct phys_addr_t type instead, along with all other variables in this driver that hold a physical address. The gicv5 driver correctly uses u64 variables, while all other irqchip drivers don't call virt_to_phys or similar interfaces. It's expected that other device drivers...
CVE-2026-23085
In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Avoid truncating memory addresses On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem allocations to be backed by addresses physical memory above the 32-bit address limit, as found while experimenting with larger VMSPLIT configurations. This caused the qemu virt model to crash in the GICv3 driver, which allocates the 'itt' object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses for ZONE_NORMAL, and the ITS driver stores the physical address in a 32-bit 'unsigned long' variable. Change the itt_addr variable to the correct phys_addr_t type instead, along with all other variables in this driver that hold a physical address. The gicv5 driver correctly uses u64 variables, while all other irqchip drivers don't call virt_to_phys or similar interfaces. It's expected that other device drive
CVE-2026-23085
In the Linux kernel, the following vulnerability has been resolved: i ...
GHSA-v2xc-c9fw-v73w
In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Avoid truncating memory addresses On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem allocations to be backed by addresses physical memory above the 32-bit address limit, as found while experimenting with larger VMSPLIT configurations. This caused the qemu virt model to crash in the GICv3 driver, which allocates the 'itt' object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses for ZONE_NORMAL, and the ITS driver stores the physical address in a 32-bit 'unsigned long' variable. Change the itt_addr variable to the correct phys_addr_t type instead, along with all other variables in this driver that hold a physical address. The gicv5 driver correctly uses u64 variables, while all other irqchip drivers don't call virt_to_phys or similar interfaces. It's expected that other device dr...
BDU:2026-11566
Уязвимость компонента irqchip/irq-gic-v3-its.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260930-80-0136
Уязвимость kernel-lt
ROS-20260930-73-0098
Уязвимость kernel-lt
SUSE-SU-2026:1078-1
Security update for the Linux Kernel
ELSA-2026-50232
ELSA-2026-50232: Unbreakable Enterprise kernel security update (IMPORTANT)
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-50145
ELSA-2026-50145: Unbreakable Enterprise kernel security update (IMPORTANT)
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-3750
ALT-PU-2026-3750: package `kernel-image-un-def` update to version 6.1.163-alt1
ALT-PU-2026-3601
ALT-PU-2026-3601: package `kernel-image-6.12` update to version 6.12.68-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-23085 In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Avoid truncating memory addresses On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem allocations to be backed by addresses physical memory above the 32-bit address limit, as found while experimenting with larger VMSPLIT configurations. This caused the qemu virt model to crash in the GICv3 driver, which allocates the 'itt' object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses for ZONE_NORMAL, and the ITS driver stores the physical address in a 32-bit 'unsigned long' variable. Change the itt_addr variable to the correct phys_addr_t type instead, along with all other variables in this driver that hold a physical address. The gicv5 driver correctly uses u64 variables, while all other irqchip drivers don't call virt_to_phys or similar interfaces. It's expected that other device drivers... | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
CVE-2026-23085 In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Avoid truncating memory addresses On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem allocations to be backed by addresses physical memory above the 32-bit address limit, as found while experimenting with larger VMSPLIT configurations. This caused the qemu virt model to crash in the GICv3 driver, which allocates the 'itt' object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses for ZONE_NORMAL, and the ITS driver stores the physical address in a 32-bit 'unsigned long' variable. Change the itt_addr variable to the correct phys_addr_t type instead, along with all other variables in this driver that hold a physical address. The gicv5 driver correctly uses u64 variables, while all other irqchip drivers don't call virt_to_phys or similar interfaces. It's expected that other device drivers... | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
CVE-2026-23085 In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Avoid truncating memory addresses On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem allocations to be backed by addresses physical memory above the 32-bit address limit, as found while experimenting with larger VMSPLIT configurations. This caused the qemu virt model to crash in the GICv3 driver, which allocates the 'itt' object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses for ZONE_NORMAL, and the ITS driver stores the physical address in a 32-bit 'unsigned long' variable. Change the itt_addr variable to the correct phys_addr_t type instead, along with all other variables in this driver that hold a physical address. The gicv5 driver correctly uses u64 variables, while all other irqchip drivers don't call virt_to_phys or similar interfaces. It's expected that other device drive | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
CVE-2026-23085 In the Linux kernel, the following vulnerability has been resolved: i ... | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
GHSA-v2xc-c9fw-v73w In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Avoid truncating memory addresses On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem allocations to be backed by addresses physical memory above the 32-bit address limit, as found while experimenting with larger VMSPLIT configurations. This caused the qemu virt model to crash in the GICv3 driver, which allocates the 'itt' object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses for ZONE_NORMAL, and the ITS driver stores the physical address in a 32-bit 'unsigned long' variable. Change the itt_addr variable to the correct phys_addr_t type instead, along with all other variables in this driver that hold a physical address. The gicv5 driver correctly uses u64 variables, while all other irqchip drivers don't call virt_to_phys or similar interfaces. It's expected that other device dr... | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
BDU:2026-11566 Уязвимость компонента irqchip/irq-gic-v3-its.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
ROS-20260930-80-0136 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад | |
ROS-20260930-73-0098 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад | |
SUSE-SU-2026:1078-1 Security update for the Linux Kernel | 8 месяцев назад | |||
ELSA-2026-50232 ELSA-2026-50232: Unbreakable Enterprise kernel security update (IMPORTANT) | 7 месяцев назад | |||
ALT-PU-2026-3821 ALT-PU-2026-3821: package `kernel-image-rt` update to version 5.10.250-alt1.rt145 | CVSS3: 9.8 | 9 месяцев назад | ||
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-50145 ELSA-2026-50145: Unbreakable Enterprise kernel security update (IMPORTANT) | 8 месяцев назад | |||
ELSA-2026-50160 ELSA-2026-50160: Unbreakable Enterprise kernel security update (IMPORTANT) | 8 месяцев назад | |||
SUSE-SU-2026:0962-1 Security update for the Linux Kernel | 8 месяцев назад | |||
SUSE-SU-2026:1081-1 Security update for the Linux Kernel | 8 месяцев назад | |||
ALT-PU-2026-5135 ALT-PU-2026-5135: package `kernel-image-6.18` update to version 6.18.20-alt1 | CVSS3: 9.8 | 8 месяцев назад | ||
openSUSE-SU-2026:20416-1 Security update for the Linux Kernel | 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-3601 ALT-PU-2026-3601: package `kernel-image-6.12` update to version 6.12.68-alt1 | CVSS3: 8.8 | 9 месяцев назад |
Уязвимостей на страницу