Поиск уязвимостей
Количество 19
Количество 19
CVE-2026-23088
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix crash on synthetic stacktrace field usage When creating a synthetic event based on an existing synthetic event that had a stacktrace field and the new synthetic event used that field a kernel crash occurred: ~# cd /sys/kernel/tracing ~# echo 's:stack unsigned long stack[];' > dynamic_events ~# echo 'hist:keys=prev_pid:s0=common_stacktrace if prev_state & 3' >> events/sched/sched_switch/trigger ~# echo 'hist:keys=next_pid:s1=$s0:onmatch(sched.sched_switch).trace(stack,$s1)' >> events/sched/sched_switch/trigger The above creates a synthetic event that takes a stacktrace when a task schedules out in a non-running state and passes that stacktrace to the sched_switch event when that task schedules back in. It triggers the "stack" synthetic event that has a stacktrace as its field (called "stack"). ~# echo 's:syscall_stack s64 id; unsigned long stack[];' >> dynamic_events ~# echo 'hist:keys=common_pid:s2=stac...
CVE-2026-23088
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix crash on synthetic stacktrace field usage When creating a synthetic event based on an existing synthetic event that had a stacktrace field and the new synthetic event used that field a kernel crash occurred: ~# cd /sys/kernel/tracing ~# echo 's:stack unsigned long stack[];' > dynamic_events ~# echo 'hist:keys=prev_pid:s0=common_stacktrace if prev_state & 3' >> events/sched/sched_switch/trigger ~# echo 'hist:keys=next_pid:s1=$s0:onmatch(sched.sched_switch).trace(stack,$s1)' >> events/sched/sched_switch/trigger The above creates a synthetic event that takes a stacktrace when a task schedules out in a non-running state and passes that stacktrace to the sched_switch event when that task schedules back in. It triggers the "stack" synthetic event that has a stacktrace as its field (called "stack"). ~# echo 's:syscall_stack s64 id; unsigned long stack[];' >> dynamic_events ~# echo 'hist:keys=common_pid:s2=stac...
CVE-2026-23088
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix crash on synthetic stacktrace field usage When creating a synthetic event based on an existing synthetic event that had a stacktrace field and the new synthetic event used that field a kernel crash occurred: ~# cd /sys/kernel/tracing ~# echo 's:stack unsigned long stack[];' > dynamic_events ~# echo 'hist:keys=prev_pid:s0=common_stacktrace if prev_state & 3' >> events/sched/sched_switch/trigger ~# echo 'hist:keys=next_pid:s1=$s0:onmatch(sched.sched_switch).trace(stack,$s1)' >> events/sched/sched_switch/trigger The above creates a synthetic event that takes a stacktrace when a task schedules out in a non-running state and passes that stacktrace to the sched_switch event when that task schedules back in. It triggers the "stack" synthetic event that has a stacktrace as its field (called "stack"). ~# echo 's:syscall_stack s64 id; unsigned long stack[];' >> dynamic_events ~# echo 'hist:keys=common_pid
CVE-2026-23088
tracing: Fix crash on synthetic stacktrace field usage
CVE-2026-23088
In the Linux kernel, the following vulnerability has been resolved: t ...
GHSA-3gp7-mv7f-66rh
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix crash on synthetic stacktrace field usage When creating a synthetic event based on an existing synthetic event that had a stacktrace field and the new synthetic event used that field a kernel crash occurred: ~# cd /sys/kernel/tracing ~# echo 's:stack unsigned long stack[];' > dynamic_events ~# echo 'hist:keys=prev_pid:s0=common_stacktrace if prev_state & 3' >> events/sched/sched_switch/trigger ~# echo 'hist:keys=next_pid:s1=$s0:onmatch(sched.sched_switch).trace(stack,$s1)' >> events/sched/sched_switch/trigger The above creates a synthetic event that takes a stacktrace when a task schedules out in a non-running state and passes that stacktrace to the sched_switch event when that task schedules back in. It triggers the "stack" synthetic event that has a stacktrace as its field (called "stack"). ~# echo 's:syscall_stack s64 id; unsigned long stack[];' >> dynamic_events ~# echo 'hist:keys=common_...
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-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
ALT-PU-2026-6044
ALT-PU-2026-6044: package `kernel-image-rpi-un` update to version 6.12.79-alt1
ALT-PU-2026-9924
ALT-PU-2026-9924: package `kernel-image-rpi-un` update to version 6.12.94-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-23088 In the Linux kernel, the following vulnerability has been resolved: tracing: Fix crash on synthetic stacktrace field usage When creating a synthetic event based on an existing synthetic event that had a stacktrace field and the new synthetic event used that field a kernel crash occurred: ~# cd /sys/kernel/tracing ~# echo 's:stack unsigned long stack[];' > dynamic_events ~# echo 'hist:keys=prev_pid:s0=common_stacktrace if prev_state & 3' >> events/sched/sched_switch/trigger ~# echo 'hist:keys=next_pid:s1=$s0:onmatch(sched.sched_switch).trace(stack,$s1)' >> events/sched/sched_switch/trigger The above creates a synthetic event that takes a stacktrace when a task schedules out in a non-running state and passes that stacktrace to the sched_switch event when that task schedules back in. It triggers the "stack" synthetic event that has a stacktrace as its field (called "stack"). ~# echo 's:syscall_stack s64 id; unsigned long stack[];' >> dynamic_events ~# echo 'hist:keys=common_pid:s2=stac... | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
CVE-2026-23088 In the Linux kernel, the following vulnerability has been resolved: tracing: Fix crash on synthetic stacktrace field usage When creating a synthetic event based on an existing synthetic event that had a stacktrace field and the new synthetic event used that field a kernel crash occurred: ~# cd /sys/kernel/tracing ~# echo 's:stack unsigned long stack[];' > dynamic_events ~# echo 'hist:keys=prev_pid:s0=common_stacktrace if prev_state & 3' >> events/sched/sched_switch/trigger ~# echo 'hist:keys=next_pid:s1=$s0:onmatch(sched.sched_switch).trace(stack,$s1)' >> events/sched/sched_switch/trigger The above creates a synthetic event that takes a stacktrace when a task schedules out in a non-running state and passes that stacktrace to the sched_switch event when that task schedules back in. It triggers the "stack" synthetic event that has a stacktrace as its field (called "stack"). ~# echo 's:syscall_stack s64 id; unsigned long stack[];' >> dynamic_events ~# echo 'hist:keys=common_pid:s2=stac... | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
CVE-2026-23088 In the Linux kernel, the following vulnerability has been resolved: tracing: Fix crash on synthetic stacktrace field usage When creating a synthetic event based on an existing synthetic event that had a stacktrace field and the new synthetic event used that field a kernel crash occurred: ~# cd /sys/kernel/tracing ~# echo 's:stack unsigned long stack[];' > dynamic_events ~# echo 'hist:keys=prev_pid:s0=common_stacktrace if prev_state & 3' >> events/sched/sched_switch/trigger ~# echo 'hist:keys=next_pid:s1=$s0:onmatch(sched.sched_switch).trace(stack,$s1)' >> events/sched/sched_switch/trigger The above creates a synthetic event that takes a stacktrace when a task schedules out in a non-running state and passes that stacktrace to the sched_switch event when that task schedules back in. It triggers the "stack" synthetic event that has a stacktrace as its field (called "stack"). ~# echo 's:syscall_stack s64 id; unsigned long stack[];' >> dynamic_events ~# echo 'hist:keys=common_pid | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
CVE-2026-23088 tracing: Fix crash on synthetic stacktrace field usage | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад | |
CVE-2026-23088 In the Linux kernel, the following vulnerability has been resolved: t ... | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
GHSA-3gp7-mv7f-66rh In the Linux kernel, the following vulnerability has been resolved: tracing: Fix crash on synthetic stacktrace field usage When creating a synthetic event based on an existing synthetic event that had a stacktrace field and the new synthetic event used that field a kernel crash occurred: ~# cd /sys/kernel/tracing ~# echo 's:stack unsigned long stack[];' > dynamic_events ~# echo 'hist:keys=prev_pid:s0=common_stacktrace if prev_state & 3' >> events/sched/sched_switch/trigger ~# echo 'hist:keys=next_pid:s1=$s0:onmatch(sched.sched_switch).trace(stack,$s1)' >> events/sched/sched_switch/trigger The above creates a synthetic event that takes a stacktrace when a task schedules out in a non-running state and passes that stacktrace to the sched_switch event when that task schedules back in. It triggers the "stack" synthetic event that has a stacktrace as its field (called "stack"). ~# echo 's:syscall_stack s64 id; unsigned long stack[];' >> dynamic_events ~# echo 'hist:keys=common_... | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
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-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 месяцев назад | ||
ALT-PU-2026-6044 ALT-PU-2026-6044: package `kernel-image-rpi-un` update to version 6.12.79-alt1 | CVSS3: 9.8 | 7 месяцев назад | ||
ALT-PU-2026-9924 ALT-PU-2026-9924: package `kernel-image-rpi-un` update to version 6.12.94-alt1 | CVSS3: 10 | 5 месяцев назад |
Уязвимостей на страницу