Поиск уязвимостей
Количество 16
Количество 16
CVE-2024-26706
In the Linux kernel, the following vulnerability has been resolved: parisc: Fix random data corruption from exception handler The current exception handler implementation, which assists when accessing user space memory, may exhibit random data corruption if the compiler decides to use a different register than the specified register %r29 (defined in ASM_EXCEPTIONTABLE_REG) for the error code. If the compiler choose another register, the fault handler will nevertheless store -EFAULT into %r29 and thus trash whatever this register is used for. Looking at the assembly I found that this happens sometimes in emulate_ldd(). To solve the issue, the easiest solution would be if it somehow is possible to tell the fault handler which register is used to hold the error code. Using %0 or %1 in the inline assembly is not posssible as it will show up as e.g. %r29 (with the "%r" prefix), which the GNU assembler can not convert to an integer. This patch takes another, better and more flexible appro...
CVE-2024-26706
In the Linux kernel, the following vulnerability has been resolved: parisc: Fix random data corruption from exception handler The current exception handler implementation, which assists when accessing user space memory, may exhibit random data corruption if the compiler decides to use a different register than the specified register %r29 (defined in ASM_EXCEPTIONTABLE_REG) for the error code. If the compiler choose another register, the fault handler will nevertheless store -EFAULT into %r29 and thus trash whatever this register is used for. Looking at the assembly I found that this happens sometimes in emulate_ldd(). To solve the issue, the easiest solution would be if it somehow is possible to tell the fault handler which register is used to hold the error code. Using %0 or %1 in the inline assembly is not posssible as it will show up as e.g. %r29 (with the "%r" prefix), which the GNU assembler can not convert to an integer. This patch takes another, better and more flexible appro...
CVE-2024-26706
In the Linux kernel, the following vulnerability has been resolved: parisc: Fix random data corruption from exception handler The current exception handler implementation, which assists when accessing user space memory, may exhibit random data corruption if the compiler decides to use a different register than the specified register %r29 (defined in ASM_EXCEPTIONTABLE_REG) for the error code. If the compiler choose another register, the fault handler will nevertheless store -EFAULT into %r29 and thus trash whatever this register is used for. Looking at the assembly I found that this happens sometimes in emulate_ldd(). To solve the issue, the easiest solution would be if it somehow is possible to tell the fault handler which register is used to hold the error code. Using %0 or %1 in the inline assembly is not posssible as it will show up as e.g. %r29 (with the "%r" prefix), which the GNU assembler can not convert to an integer. This patch takes another, better and more flexible appr
CVE-2024-26706
parisc: Fix random data corruption from exception handler
CVE-2024-26706
In the Linux kernel, the following vulnerability has been resolved: p ...
GHSA-4fj7-85cf-9m8p
In the Linux kernel, the following vulnerability has been resolved: parisc: Fix random data corruption from exception handler The current exception handler implementation, which assists when accessing user space memory, may exhibit random data corruption if the compiler decides to use a different register than the specified register %r29 (defined in ASM_EXCEPTIONTABLE_REG) for the error code. If the compiler choose another register, the fault handler will nevertheless store -EFAULT into %r29 and thus trash whatever this register is used for. Looking at the assembly I found that this happens sometimes in emulate_ldd(). To solve the issue, the easiest solution would be if it somehow is possible to tell the fault handler which register is used to hold the error code. Using %0 or %1 in the inline assembly is not posssible as it will show up as e.g. %r29 (with the "%r" prefix), which the GNU assembler can not convert to an integer. This patch takes another, better and more flexible a...
BDU:2025-13306
Уязвимость компонента parisc ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20251021-02
Множественные уязвимости kernel-lt
ALT-PU-2024-2868
ALT-PU-2024-2868: package `kernel-image-un-def` update to version 6.1.79-alt1
ALT-PU-2024-18361
ALT-PU-2024-18361: package `kernel-image-std-def` update to version 6.1.79-alt1
ALT-PU-2024-3144
ALT-PU-2024-3144: package `kernel-image-rt` update to version 6.1.79-alt1.rt25
ALT-PU-2024-18464
ALT-PU-2024-18464: package `kernel-image-un-def` update to version 6.6.18-alt1
ALT-PU-2024-18207
ALT-PU-2024-18207: package `kernel-image-pine` update to version 6.6.18-alt1
ALT-PU-2024-3415
ALT-PU-2024-3415: package `kernel-image-mp` update to version 6.7.8-alt1
ALT-PU-2024-6818
ALT-PU-2024-6818: package `kernel-image-rpi-un` update to version 6.6.23-alt1
ALT-PU-2024-14046
ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-26706 In the Linux kernel, the following vulnerability has been resolved: parisc: Fix random data corruption from exception handler The current exception handler implementation, which assists when accessing user space memory, may exhibit random data corruption if the compiler decides to use a different register than the specified register %r29 (defined in ASM_EXCEPTIONTABLE_REG) for the error code. If the compiler choose another register, the fault handler will nevertheless store -EFAULT into %r29 and thus trash whatever this register is used for. Looking at the assembly I found that this happens sometimes in emulate_ldd(). To solve the issue, the easiest solution would be if it somehow is possible to tell the fault handler which register is used to hold the error code. Using %0 or %1 in the inline assembly is not posssible as it will show up as e.g. %r29 (with the "%r" prefix), which the GNU assembler can not convert to an integer. This patch takes another, better and more flexible appro... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26706 In the Linux kernel, the following vulnerability has been resolved: parisc: Fix random data corruption from exception handler The current exception handler implementation, which assists when accessing user space memory, may exhibit random data corruption if the compiler decides to use a different register than the specified register %r29 (defined in ASM_EXCEPTIONTABLE_REG) for the error code. If the compiler choose another register, the fault handler will nevertheless store -EFAULT into %r29 and thus trash whatever this register is used for. Looking at the assembly I found that this happens sometimes in emulate_ldd(). To solve the issue, the easiest solution would be if it somehow is possible to tell the fault handler which register is used to hold the error code. Using %0 or %1 in the inline assembly is not posssible as it will show up as e.g. %r29 (with the "%r" prefix), which the GNU assembler can not convert to an integer. This patch takes another, better and more flexible appro... | CVSS3: 4.4 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26706 In the Linux kernel, the following vulnerability has been resolved: parisc: Fix random data corruption from exception handler The current exception handler implementation, which assists when accessing user space memory, may exhibit random data corruption if the compiler decides to use a different register than the specified register %r29 (defined in ASM_EXCEPTIONTABLE_REG) for the error code. If the compiler choose another register, the fault handler will nevertheless store -EFAULT into %r29 and thus trash whatever this register is used for. Looking at the assembly I found that this happens sometimes in emulate_ldd(). To solve the issue, the easiest solution would be if it somehow is possible to tell the fault handler which register is used to hold the error code. Using %0 or %1 in the inline assembly is not posssible as it will show up as e.g. %r29 (with the "%r" prefix), which the GNU assembler can not convert to an integer. This patch takes another, better and more flexible appr | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26706 parisc: Fix random data corruption from exception handler | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад | |
CVE-2024-26706 In the Linux kernel, the following vulnerability has been resolved: p ... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
GHSA-4fj7-85cf-9m8p In the Linux kernel, the following vulnerability has been resolved: parisc: Fix random data corruption from exception handler The current exception handler implementation, which assists when accessing user space memory, may exhibit random data corruption if the compiler decides to use a different register than the specified register %r29 (defined in ASM_EXCEPTIONTABLE_REG) for the error code. If the compiler choose another register, the fault handler will nevertheless store -EFAULT into %r29 and thus trash whatever this register is used for. Looking at the assembly I found that this happens sometimes in emulate_ldd(). To solve the issue, the easiest solution would be if it somehow is possible to tell the fault handler which register is used to hold the error code. Using %0 or %1 in the inline assembly is not posssible as it will show up as e.g. %r29 (with the "%r" prefix), which the GNU assembler can not convert to an integer. This patch takes another, better and more flexible a... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
BDU:2025-13306 Уязвимость компонента parisc ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
ROS-20251021-02 Множественные уязвимости kernel-lt | CVSS3: 6.7 | около 1 года назад | ||
ALT-PU-2024-2868 ALT-PU-2024-2868: package `kernel-image-un-def` update to version 6.1.79-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-18361 ALT-PU-2024-18361: package `kernel-image-std-def` update to version 6.1.79-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-3144 ALT-PU-2024-3144: package `kernel-image-rt` update to version 6.1.79-alt1.rt25 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-18464 ALT-PU-2024-18464: package `kernel-image-un-def` update to version 6.6.18-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-18207 ALT-PU-2024-18207: package `kernel-image-pine` update to version 6.6.18-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-3415 ALT-PU-2024-3415: package `kernel-image-mp` update to version 6.7.8-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-6818 ALT-PU-2024-6818: package `kernel-image-rpi-un` update to version 6.6.23-alt1 | CVSS3: 9.4 | больше 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 года назад |
Уязвимостей на страницу