Поиск уязвимостей
Количество 74
Количество 74
GHSA-gm32-xqh2-ff6r
In the Linux kernel, the following vulnerability has been resolved: of_numa: fix uninitialized memory nodes causing kernel panic When there are memory-only nodes (nodes without CPUs), these nodes are not properly initialized, causing kernel panic during boot. of_numa_init of_numa_parse_cpu_nodes node_set(nid, numa_nodes_parsed); of_numa_parse_memory_nodes In of_numa_parse_cpu_nodes, numa_nodes_parsed gets updated only for nodes containing CPUs. Memory-only nodes should have been updated in of_numa_parse_memory_nodes, but they weren't. Subsequently, when free_area_init() attempts to access NODE_DATA() for these uninitialized memory nodes, the kernel panics due to NULL pointer dereference. This can be reproduced on ARM64 QEMU with 1 CPU and 2 memory nodes: qemu-system-aarch64 \ -cpu host -nographic \ -m 4G -smp 1 \ -machine virt,accel=kvm,gic-version=3,iommu=smmuv3 \ -object memory-backend-ram,size=2G,id=mem0 \ -object memory-backend-ram,size=2G,id=mem1 \ -numa node,nodeid...
BDU:2025-15668
Уязвимость компонента of_numa.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ALT-PU-2026-1529
ALT-PU-2026-1529: package `kernel-image-pine` update to version 6.12.66-alt1
GHSA-cgf5-f6fj-4v5q
In the Linux kernel, the following vulnerability has been resolved: tls: make sure to abort the stream if headers are bogus Normally we wait for the socket to buffer up the whole record before we service it. If the socket has a tiny buffer, however, we read out the data sooner, to prevent connection stalls. Make sure that we abort the connection when we find out late that the record is actually invalid. Retrying the parsing is fine in itself but since we copy some more data each time before we parse we can overflow the allocated skb space. Constructing a scenario in which we're under pressure without enough data in the socket to parse the length upfront is quite hard. syzbot figured out a way to do this by serving us the header in small OOB sends, and then filling in the recvbuf with a large normal send. Make sure that tls_rx_msg_size() aborts strp, if we reach an invalid record there's really no way to recover.
BDU:2025-12556
Уязвимость функции tls_rx_msg_size() компонента tls ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ALT-PU-2025-16600
ALT-PU-2025-16600: package `kernel-image-un-def` update to version 6.1.151-alt1
ROS-20260701-80-0005
Уязвимость kernel-lt
RLSA-2025:22405
Moderate: kernel security update
ELSA-2025-22405
ELSA-2025-22405: kernel security update (MODERATE)
SUSE-SU-2025:3751-1
Security update for the Linux Kernel
SUSE-SU-2025:03600-1
Security update for the Linux Kernel
ELSA-2025-25755
ELSA-2025-25755: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2025:03634-1
Security update for the Linux Kernel
ROS-20251202-02
Множественные уязвимости kernel-lt
SUSE-SU-2025:3725-1
Security update for the Linux Kernel
SUSE-SU-2025:03601-1
Security update for the Linux Kernel
ELSA-2025-20662
ELSA-2025-20662: Unbreakable Enterprise kernel security update (IMPORTANT)
ALT-PU-2025-16621
ALT-PU-2025-16621: package `kernel-image-rt` update to version 5.10.243-alt1.rt137
ALT-PU-2025-11619
ALT-PU-2025-11619: package `kernel-image-std-def` update to version 5.10.244-alt1
SUSE-SU-2025:03602-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
GHSA-gm32-xqh2-ff6r In the Linux kernel, the following vulnerability has been resolved: of_numa: fix uninitialized memory nodes causing kernel panic When there are memory-only nodes (nodes without CPUs), these nodes are not properly initialized, causing kernel panic during boot. of_numa_init of_numa_parse_cpu_nodes node_set(nid, numa_nodes_parsed); of_numa_parse_memory_nodes In of_numa_parse_cpu_nodes, numa_nodes_parsed gets updated only for nodes containing CPUs. Memory-only nodes should have been updated in of_numa_parse_memory_nodes, but they weren't. Subsequently, when free_area_init() attempts to access NODE_DATA() for these uninitialized memory nodes, the kernel panics due to NULL pointer dereference. This can be reproduced on ARM64 QEMU with 1 CPU and 2 memory nodes: qemu-system-aarch64 \ -cpu host -nographic \ -m 4G -smp 1 \ -machine virt,accel=kvm,gic-version=3,iommu=smmuv3 \ -object memory-backend-ram,size=2G,id=mem0 \ -object memory-backend-ram,size=2G,id=mem1 \ -numa node,nodeid... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
BDU:2025-15668 Уязвимость компонента of_numa.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 4.4 | 0% Низкий | около 1 года назад | |
ALT-PU-2026-1529 ALT-PU-2026-1529: package `kernel-image-pine` update to version 6.12.66-alt1 | CVSS3: 9.8 | 10 месяцев назад | ||
GHSA-cgf5-f6fj-4v5q In the Linux kernel, the following vulnerability has been resolved: tls: make sure to abort the stream if headers are bogus Normally we wait for the socket to buffer up the whole record before we service it. If the socket has a tiny buffer, however, we read out the data sooner, to prevent connection stalls. Make sure that we abort the connection when we find out late that the record is actually invalid. Retrying the parsing is fine in itself but since we copy some more data each time before we parse we can overflow the allocated skb space. Constructing a scenario in which we're under pressure without enough data in the socket to parse the length upfront is quite hard. syzbot figured out a way to do this by serving us the header in small OOB sends, and then filling in the recvbuf with a large normal send. Make sure that tls_rx_msg_size() aborts strp, if we reach an invalid record there's really no way to recover. | CVSS3: 5.5 | 10% Средний | около 1 года назад | |
BDU:2025-12556 Уязвимость функции tls_rx_msg_size() компонента tls ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 7 | 10% Средний | около 1 года назад | |
ALT-PU-2025-16600 ALT-PU-2025-16600: package `kernel-image-un-def` update to version 6.1.151-alt1 | CVSS3: 9.8 | около 1 года назад | ||
ROS-20260701-80-0005 Уязвимость kernel-lt | CVSS3: 4.4 | 0% Низкий | 4 месяца назад | |
RLSA-2025:22405 Moderate: kernel security update | 11 месяцев назад | |||
ELSA-2025-22405 ELSA-2025-22405: kernel security update (MODERATE) | 11 месяцев назад | |||
SUSE-SU-2025:3751-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03600-1 Security update for the Linux Kernel | около 1 года назад | |||
ELSA-2025-25755 ELSA-2025-25755: Unbreakable Enterprise kernel security update (IMPORTANT) | около 1 года назад | |||
SUSE-SU-2025:03634-1 Security update for the Linux Kernel | около 1 года назад | |||
ROS-20251202-02 Множественные уязвимости kernel-lt | CVSS2: 6.6 | 11 месяцев назад | ||
SUSE-SU-2025:3725-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03601-1 Security update for the Linux Kernel | около 1 года назад | |||
ELSA-2025-20662 ELSA-2025-20662: Unbreakable Enterprise kernel security update (IMPORTANT) | около 1 года назад | |||
ALT-PU-2025-16621 ALT-PU-2025-16621: package `kernel-image-rt` update to version 5.10.243-alt1.rt137 | CVSS3: 8 | около 1 года назад | ||
ALT-PU-2025-11619 ALT-PU-2025-11619: package `kernel-image-std-def` update to version 5.10.244-alt1 | CVSS3: 8 | около 1 года назад | ||
SUSE-SU-2025:03602-1 Security update for the Linux Kernel | около 1 года назад |
Уязвимостей на страницу