Поиск уязвимостей
Количество 17
Количество 17
CVE-2024-35871
In the Linux kernel, the following vulnerability has been resolved: riscv: process: Fix kernel gp leakage childregs represents the registers which are active for the new thread in user context. For a kernel thread, childregs->gp is never used since the kernel gp is not touched by switch_to. For a user mode helper, the gp value can be observed in user space after execve or possibly by other means. [From the email thread] The /* Kernel thread */ comment is somewhat inaccurate in that it is also used for user_mode_helper threads, which exec a user process, e.g. /sbin/init or when /proc/sys/kernel/core_pattern is a pipe. Such threads do not have PF_KTHREAD set and are valid targets for ptrace etc. even before they exec. childregs is the *user* context during syscall execution and it is observable from userspace in at least five ways: 1. kernel_execve does not currently clear integer registers, so the starting register state for PID 1 and other user processes started by the kernel has sp...
CVE-2024-35871
In the Linux kernel, the following vulnerability has been resolved: riscv: process: Fix kernel gp leakage childregs represents the registers which are active for the new thread in user context. For a kernel thread, childregs->gp is never used since the kernel gp is not touched by switch_to. For a user mode helper, the gp value can be observed in user space after execve or possibly by other means. [From the email thread] The /* Kernel thread */ comment is somewhat inaccurate in that it is also used for user_mode_helper threads, which exec a user process, e.g. /sbin/init or when /proc/sys/kernel/core_pattern is a pipe. Such threads do not have PF_KTHREAD set and are valid targets for ptrace etc. even before they exec. childregs is the *user* context during syscall execution and it is observable from userspace in at least five ways: 1. kernel_execve does not currently clear integer registers, so the starting register state for PID 1 and other user processes started by the kernel has sp...
CVE-2024-35871
In the Linux kernel, the following vulnerability has been resolved: riscv: process: Fix kernel gp leakage childregs represents the registers which are active for the new thread in user context. For a kernel thread, childregs->gp is never used since the kernel gp is not touched by switch_to. For a user mode helper, the gp value can be observed in user space after execve or possibly by other means. [From the email thread] The /* Kernel thread */ comment is somewhat inaccurate in that it is also used for user_mode_helper threads, which exec a user process, e.g. /sbin/init or when /proc/sys/kernel/core_pattern is a pipe. Such threads do not have PF_KTHREAD set and are valid targets for ptrace etc. even before they exec. childregs is the *user* context during syscall execution and it is observable from userspace in at least five ways: 1. kernel_execve does not currently clear integer registers, so the starting register state for PID 1 and other user processes started by the kernel
CVE-2024-35871
In the Linux kernel, the following vulnerability has been resolved: r ...
GHSA-wjqf-4c62-v6g5
In the Linux kernel, the following vulnerability has been resolved: riscv: process: Fix kernel gp leakage childregs represents the registers which are active for the new thread in user context. For a kernel thread, childregs->gp is never used since the kernel gp is not touched by switch_to. For a user mode helper, the gp value can be observed in user space after execve or possibly by other means. [From the email thread] The /* Kernel thread */ comment is somewhat inaccurate in that it is also used for user_mode_helper threads, which exec a user process, e.g. /sbin/init or when /proc/sys/kernel/core_pattern is a pipe. Such threads do not have PF_KTHREAD set and are valid targets for ptrace etc. even before they exec. childregs is the *user* context during syscall execution and it is observable from userspace in at least five ways: 1. kernel_execve does not currently clear integer registers, so the starting register state for PID 1 and other user processes started by the kern...
BDU:2024-10059
Уязвимость компонента riscv ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20241118-01
Множественные уязвимости kernel-lt
ALT-PU-2024-18367
ALT-PU-2024-18367: package `kernel-image-std-def` update to version 6.1.85-alt1
ALT-PU-2024-18060
ALT-PU-2024-18060: package `kernel-image-un-def` update to version 6.1.85-alt1
ALT-PU-2024-18078
ALT-PU-2024-18078: package `kernel-image-rt` update to version 5.10.216-alt1.rt108
ALT-PU-2024-18471
ALT-PU-2024-18471: package `kernel-image-un-def` update to version 6.6.26-alt1
ALT-PU-2024-18144
ALT-PU-2024-18144: package `kernel-image-6.8` update to version 6.8.5-alt1
ALT-PU-2024-18212
ALT-PU-2024-18212: package `kernel-image-pine` update to version 6.6.27-alt1
ALT-PU-2024-18118
ALT-PU-2024-18118: package `kernel-image-mp` update to version 6.8.8-alt1
ALT-PU-2024-7511
ALT-PU-2024-7511: package `kernel-image-std-def` update to version 5.10.216-alt1
ALT-PU-2024-7646
ALT-PU-2024-7646: package `kernel-image-rt` update to version 6.1.90-alt1.rt30
ALT-PU-2024-14046
ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-35871 In the Linux kernel, the following vulnerability has been resolved: riscv: process: Fix kernel gp leakage childregs represents the registers which are active for the new thread in user context. For a kernel thread, childregs->gp is never used since the kernel gp is not touched by switch_to. For a user mode helper, the gp value can be observed in user space after execve or possibly by other means. [From the email thread] The /* Kernel thread */ comment is somewhat inaccurate in that it is also used for user_mode_helper threads, which exec a user process, e.g. /sbin/init or when /proc/sys/kernel/core_pattern is a pipe. Such threads do not have PF_KTHREAD set and are valid targets for ptrace etc. even before they exec. childregs is the *user* context during syscall execution and it is observable from userspace in at least five ways: 1. kernel_execve does not currently clear integer registers, so the starting register state for PID 1 and other user processes started by the kernel has sp... | CVSS3: 7.1 | 0% Низкий | больше 2 лет назад | |
CVE-2024-35871 In the Linux kernel, the following vulnerability has been resolved: riscv: process: Fix kernel gp leakage childregs represents the registers which are active for the new thread in user context. For a kernel thread, childregs->gp is never used since the kernel gp is not touched by switch_to. For a user mode helper, the gp value can be observed in user space after execve or possibly by other means. [From the email thread] The /* Kernel thread */ comment is somewhat inaccurate in that it is also used for user_mode_helper threads, which exec a user process, e.g. /sbin/init or when /proc/sys/kernel/core_pattern is a pipe. Such threads do not have PF_KTHREAD set and are valid targets for ptrace etc. even before they exec. childregs is the *user* context during syscall execution and it is observable from userspace in at least five ways: 1. kernel_execve does not currently clear integer registers, so the starting register state for PID 1 and other user processes started by the kernel has sp... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-35871 In the Linux kernel, the following vulnerability has been resolved: riscv: process: Fix kernel gp leakage childregs represents the registers which are active for the new thread in user context. For a kernel thread, childregs->gp is never used since the kernel gp is not touched by switch_to. For a user mode helper, the gp value can be observed in user space after execve or possibly by other means. [From the email thread] The /* Kernel thread */ comment is somewhat inaccurate in that it is also used for user_mode_helper threads, which exec a user process, e.g. /sbin/init or when /proc/sys/kernel/core_pattern is a pipe. Such threads do not have PF_KTHREAD set and are valid targets for ptrace etc. even before they exec. childregs is the *user* context during syscall execution and it is observable from userspace in at least five ways: 1. kernel_execve does not currently clear integer registers, so the starting register state for PID 1 and other user processes started by the kernel | CVSS3: 7.1 | 0% Низкий | больше 2 лет назад | |
CVE-2024-35871 In the Linux kernel, the following vulnerability has been resolved: r ... | CVSS3: 7.1 | 0% Низкий | больше 2 лет назад | |
GHSA-wjqf-4c62-v6g5 In the Linux kernel, the following vulnerability has been resolved: riscv: process: Fix kernel gp leakage childregs represents the registers which are active for the new thread in user context. For a kernel thread, childregs->gp is never used since the kernel gp is not touched by switch_to. For a user mode helper, the gp value can be observed in user space after execve or possibly by other means. [From the email thread] The /* Kernel thread */ comment is somewhat inaccurate in that it is also used for user_mode_helper threads, which exec a user process, e.g. /sbin/init or when /proc/sys/kernel/core_pattern is a pipe. Such threads do not have PF_KTHREAD set and are valid targets for ptrace etc. even before they exec. childregs is the *user* context during syscall execution and it is observable from userspace in at least five ways: 1. kernel_execve does not currently clear integer registers, so the starting register state for PID 1 and other user processes started by the kern... | CVSS3: 7.1 | 0% Низкий | больше 2 лет назад | |
BDU:2024-10059 Уязвимость компонента riscv ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
ROS-20241118-01 Множественные уязвимости kernel-lt | CVSS3: 8.8 | почти 2 года назад | ||
ALT-PU-2024-18367 ALT-PU-2024-18367: package `kernel-image-std-def` update to version 6.1.85-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-18060 ALT-PU-2024-18060: package `kernel-image-un-def` update to version 6.1.85-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-18078 ALT-PU-2024-18078: package `kernel-image-rt` update to version 5.10.216-alt1.rt108 | CVSS3: 9.1 | больше 2 лет назад | ||
ALT-PU-2024-18471 ALT-PU-2024-18471: package `kernel-image-un-def` update to version 6.6.26-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-18144 ALT-PU-2024-18144: package `kernel-image-6.8` update to version 6.8.5-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-18212 ALT-PU-2024-18212: package `kernel-image-pine` update to version 6.6.27-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-18118 ALT-PU-2024-18118: package `kernel-image-mp` update to version 6.8.8-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-7511 ALT-PU-2024-7511: package `kernel-image-std-def` update to version 5.10.216-alt1 | CVSS3: 9.1 | больше 2 лет назад | ||
ALT-PU-2024-7646 ALT-PU-2024-7646: package `kernel-image-rt` update to version 6.1.90-alt1.rt30 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-14046 ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1 | CVSS3: 9.8 | почти 2 года назад |
Уязвимостей на страницу