Поиск уязвимостей
Количество 22
Количество 22
CVE-2026-23107
In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA The code to restore a ZA context doesn't attempt to allocate the task's sve_state before setting TIF_SME. Consequently, restoring a ZA context can place a task into an invalid state where TIF_SME is set but the task's sve_state is NULL. In legitimate but uncommon cases where the ZA signal context was NOT created by the kernel in the context of the same task (e.g. if the task is saved/restored with something like CRIU), we have no guarantee that sve_state had been allocated previously. In these cases, userspace can enter streaming mode without trapping while sve_state is NULL, causing a later NULL pointer dereference when the kernel attempts to store the register state: | # ./sigreturn-za | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 | Mem abort info: | ESR = 0x0000000096000046 | EC = 0x25: DABT (current EL), IL...
CVE-2026-23107
In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA The code to restore a ZA context doesn't attempt to allocate the task's sve_state before setting TIF_SME. Consequently, restoring a ZA context can place a task into an invalid state where TIF_SME is set but the task's sve_state is NULL. In legitimate but uncommon cases where the ZA signal context was NOT created by the kernel in the context of the same task (e.g. if the task is saved/restored with something like CRIU), we have no guarantee that sve_state had been allocated previously. In these cases, userspace can enter streaming mode without trapping while sve_state is NULL, causing a later NULL pointer dereference when the kernel attempts to store the register state: | # ./sigreturn-za | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 | Mem abort info: | ESR = 0x0000000096000046 | EC = 0x25: DABT (current EL), IL...
CVE-2026-23107
In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA The code to restore a ZA context doesn't attempt to allocate the task's sve_state before setting TIF_SME. Consequently, restoring a ZA context can place a task into an invalid state where TIF_SME is set but the task's sve_state is NULL. In legitimate but uncommon cases where the ZA signal context was NOT created by the kernel in the context of the same task (e.g. if the task is saved/restored with something like CRIU), we have no guarantee that sve_state had been allocated previously. In these cases, userspace can enter streaming mode without trapping while sve_state is NULL, causing a later NULL pointer dereference when the kernel attempts to store the register state: | # ./sigreturn-za | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 | Mem abort info: | ESR = 0x0000000096000046 | EC = 0x25: DABT (current EL), I
CVE-2026-23107
In the Linux kernel, the following vulnerability has been resolved: a ...
GHSA-7xwr-6p6c-h357
In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA The code to restore a ZA context doesn't attempt to allocate the task's sve_state before setting TIF_SME. Consequently, restoring a ZA context can place a task into an invalid state where TIF_SME is set but the task's sve_state is NULL. In legitimate but uncommon cases where the ZA signal context was NOT created by the kernel in the context of the same task (e.g. if the task is saved/restored with something like CRIU), we have no guarantee that sve_state had been allocated previously. In these cases, userspace can enter streaming mode without trapping while sve_state is NULL, causing a later NULL pointer dereference when the kernel attempts to store the register state: | # ./sigreturn-za | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 | Mem abort info: | ESR = 0x0000000096000046 | EC = 0x25: DABT (current EL)...
BDU:2026-11578
Уязвимость компонента arch/arm64/kernel/signal.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260930-80-0149
Уязвимость kernel-lt
ROS-20260930-73-0109
Уязвимость kernel-lt
ELSA-2026-50232
ELSA-2026-50232: 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
ALT-PU-2026-3600
ALT-PU-2026-3600: package `kernel-image-rt` update to version 6.12.68-alt1
ALT-PU-2026-4046
ALT-PU-2026-4046: package `kernel-image-pine` update to version 6.18.13-alt1
ELSA-2026-50372
ELSA-2026-50372: Unbreakable Enterprise kernel security update (IMPORTANT)
ALT-PU-2026-4865
ALT-PU-2026-4865: package `kernel-image-6.18` update to version 6.18.19-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-23107 In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA The code to restore a ZA context doesn't attempt to allocate the task's sve_state before setting TIF_SME. Consequently, restoring a ZA context can place a task into an invalid state where TIF_SME is set but the task's sve_state is NULL. In legitimate but uncommon cases where the ZA signal context was NOT created by the kernel in the context of the same task (e.g. if the task is saved/restored with something like CRIU), we have no guarantee that sve_state had been allocated previously. In these cases, userspace can enter streaming mode without trapping while sve_state is NULL, causing a later NULL pointer dereference when the kernel attempts to store the register state: | # ./sigreturn-za | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 | Mem abort info: | ESR = 0x0000000096000046 | EC = 0x25: DABT (current EL), IL... | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
CVE-2026-23107 In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA The code to restore a ZA context doesn't attempt to allocate the task's sve_state before setting TIF_SME. Consequently, restoring a ZA context can place a task into an invalid state where TIF_SME is set but the task's sve_state is NULL. In legitimate but uncommon cases where the ZA signal context was NOT created by the kernel in the context of the same task (e.g. if the task is saved/restored with something like CRIU), we have no guarantee that sve_state had been allocated previously. In these cases, userspace can enter streaming mode without trapping while sve_state is NULL, causing a later NULL pointer dereference when the kernel attempts to store the register state: | # ./sigreturn-za | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 | Mem abort info: | ESR = 0x0000000096000046 | EC = 0x25: DABT (current EL), IL... | CVSS3: 6.2 | 0% Низкий | 9 месяцев назад | |
CVE-2026-23107 In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA The code to restore a ZA context doesn't attempt to allocate the task's sve_state before setting TIF_SME. Consequently, restoring a ZA context can place a task into an invalid state where TIF_SME is set but the task's sve_state is NULL. In legitimate but uncommon cases where the ZA signal context was NOT created by the kernel in the context of the same task (e.g. if the task is saved/restored with something like CRIU), we have no guarantee that sve_state had been allocated previously. In these cases, userspace can enter streaming mode without trapping while sve_state is NULL, causing a later NULL pointer dereference when the kernel attempts to store the register state: | # ./sigreturn-za | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 | Mem abort info: | ESR = 0x0000000096000046 | EC = 0x25: DABT (current EL), I | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
CVE-2026-23107 In the Linux kernel, the following vulnerability has been resolved: a ... | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
GHSA-7xwr-6p6c-h357 In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA The code to restore a ZA context doesn't attempt to allocate the task's sve_state before setting TIF_SME. Consequently, restoring a ZA context can place a task into an invalid state where TIF_SME is set but the task's sve_state is NULL. In legitimate but uncommon cases where the ZA signal context was NOT created by the kernel in the context of the same task (e.g. if the task is saved/restored with something like CRIU), we have no guarantee that sve_state had been allocated previously. In these cases, userspace can enter streaming mode without trapping while sve_state is NULL, causing a later NULL pointer dereference when the kernel attempts to store the register state: | # ./sigreturn-za | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 | Mem abort info: | ESR = 0x0000000096000046 | EC = 0x25: DABT (current EL)... | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
BDU:2026-11578 Уязвимость компонента arch/arm64/kernel/signal.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
ROS-20260930-80-0149 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад | |
ROS-20260930-73-0109 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад | |
ELSA-2026-50232 ELSA-2026-50232: Unbreakable Enterprise kernel security update (IMPORTANT) | 7 месяцев назад | |||
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 месяцев назад | ||
ALT-PU-2026-3600 ALT-PU-2026-3600: package `kernel-image-rt` update to version 6.12.68-alt1 | CVSS3: 8.8 | 9 месяцев назад | ||
ALT-PU-2026-4046 ALT-PU-2026-4046: package `kernel-image-pine` update to version 6.18.13-alt1 | CVSS3: 9.8 | 9 месяцев назад | ||
ELSA-2026-50372 ELSA-2026-50372: Unbreakable Enterprise kernel security update (IMPORTANT) | 4 месяца назад | |||
ALT-PU-2026-4865 ALT-PU-2026-4865: package `kernel-image-6.18` update to version 6.18.19-alt1 | CVSS3: 9.8 | 7 месяцев назад |
Уязвимостей на страницу