Поиск уязвимостей
Количество 16
Количество 16
CVE-2023-53642
In the Linux kernel, the following vulnerability has been resolved: x86: fix clear_user_rep_good() exception handling annotation This code no longer exists in mainline, because it was removed in commit d2c95f9d6802 ("x86: don't use REP_GOOD or ERMS for user memory clearing") upstream. However, rather than backport the full range of x86 memory clearing and copying cleanups, fix the exception table annotation placement for the final 'rep movsb' in clear_user_rep_good(): rather than pointing at the actual instruction that did the user space access, it pointed to the register move just before it. That made sense from a code flow standpoint, but not from an actual usage standpoint: it means that if user access takes an exception, the exception handler won't actually find the instruction in the exception tables. As a result, rather than fixing it up and returning -EFAULT, it would then turn it into a kernel oops report instead, something like: BUG: unable to handle page fault for address:...
CVE-2023-53642
In the Linux kernel, the following vulnerability has been resolved: x86: fix clear_user_rep_good() exception handling annotation This code no longer exists in mainline, because it was removed in commit d2c95f9d6802 ("x86: don't use REP_GOOD or ERMS for user memory clearing") upstream. However, rather than backport the full range of x86 memory clearing and copying cleanups, fix the exception table annotation placement for the final 'rep movsb' in clear_user_rep_good(): rather than pointing at the actual instruction that did the user space access, it pointed to the register move just before it. That made sense from a code flow standpoint, but not from an actual usage standpoint: it means that if user access takes an exception, the exception handler won't actually find the instruction in the exception tables. As a result, rather than fixing it up and returning -EFAULT, it would then turn it into a kernel oops report instead, something like: BUG: unable to handle page fault for address:...
CVE-2023-53642
In the Linux kernel, the following vulnerability has been resolved: x86: fix clear_user_rep_good() exception handling annotation This code no longer exists in mainline, because it was removed in commit d2c95f9d6802 ("x86: don't use REP_GOOD or ERMS for user memory clearing") upstream. However, rather than backport the full range of x86 memory clearing and copying cleanups, fix the exception table annotation placement for the final 'rep movsb' in clear_user_rep_good(): rather than pointing at the actual instruction that did the user space access, it pointed to the register move just before it. That made sense from a code flow standpoint, but not from an actual usage standpoint: it means that if user access takes an exception, the exception handler won't actually find the instruction in the exception tables. As a result, rather than fixing it up and returning -EFAULT, it would then turn it into a kernel oops report instead, something like: BUG: unable to handle page fault for a
CVE-2023-53642
x86: fix clear_user_rep_good() exception handling annotation
CVE-2023-53642
In the Linux kernel, the following vulnerability has been resolved: x ...
GHSA-h9cf-c7q8-gcqh
In the Linux kernel, the following vulnerability has been resolved: x86: fix clear_user_rep_good() exception handling annotation This code no longer exists in mainline, because it was removed in commit d2c95f9d6802 ("x86: don't use REP_GOOD or ERMS for user memory clearing") upstream. However, rather than backport the full range of x86 memory clearing and copying cleanups, fix the exception table annotation placement for the final 'rep movsb' in clear_user_rep_good(): rather than pointing at the actual instruction that did the user space access, it pointed to the register move just before it. That made sense from a code flow standpoint, but not from an actual usage standpoint: it means that if user access takes an exception, the exception handler won't actually find the instruction in the exception tables. As a result, rather than fixing it up and returning -EFAULT, it would then turn it into a kernel oops report instead, something like: BUG: unable to handle page fault fo...
BDU:2026-03794
Уязвимость функции init_amd() модуля arch/x86/lib/clear_page_64.S ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260826-73-0005
Уязвимость kernel-lt
ALT-PU-2023-8798
ALT-PU-2023-8798: package `kernel-image-std-def` update to version 6.1.29-alt1
ALT-PU-2023-8561
ALT-PU-2023-8561: package `kernel-image-un-def` update to version 6.1.29-alt1
ALT-PU-2023-8872
ALT-PU-2023-8872: package `kernel-image-un-def` update to version 6.2.16-alt1
ALT-PU-2023-8723
ALT-PU-2023-8723: package `kernel-image-rt` update to version 6.1.33-alt1.rt11
ALT-PU-2023-1826
ALT-PU-2023-1826: package `kernel-image-mp` update to version 6.2.16-alt1
ALT-PU-2023-4663
ALT-PU-2023-4663: package `kernel-image-pine` update to version 6.4.7-alt1
ALT-PU-2024-4843
ALT-PU-2024-4843: package `kernel-image-rpi-un` update to version 6.1.77-alt1
ALT-PU-2024-4263
ALT-PU-2024-4263: package `kernel-image-rpi-un` update to version 6.1.77-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2023-53642 In the Linux kernel, the following vulnerability has been resolved: x86: fix clear_user_rep_good() exception handling annotation This code no longer exists in mainline, because it was removed in commit d2c95f9d6802 ("x86: don't use REP_GOOD or ERMS for user memory clearing") upstream. However, rather than backport the full range of x86 memory clearing and copying cleanups, fix the exception table annotation placement for the final 'rep movsb' in clear_user_rep_good(): rather than pointing at the actual instruction that did the user space access, it pointed to the register move just before it. That made sense from a code flow standpoint, but not from an actual usage standpoint: it means that if user access takes an exception, the exception handler won't actually find the instruction in the exception tables. As a result, rather than fixing it up and returning -EFAULT, it would then turn it into a kernel oops report instead, something like: BUG: unable to handle page fault for address:... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2023-53642 In the Linux kernel, the following vulnerability has been resolved: x86: fix clear_user_rep_good() exception handling annotation This code no longer exists in mainline, because it was removed in commit d2c95f9d6802 ("x86: don't use REP_GOOD or ERMS for user memory clearing") upstream. However, rather than backport the full range of x86 memory clearing and copying cleanups, fix the exception table annotation placement for the final 'rep movsb' in clear_user_rep_good(): rather than pointing at the actual instruction that did the user space access, it pointed to the register move just before it. That made sense from a code flow standpoint, but not from an actual usage standpoint: it means that if user access takes an exception, the exception handler won't actually find the instruction in the exception tables. As a result, rather than fixing it up and returning -EFAULT, it would then turn it into a kernel oops report instead, something like: BUG: unable to handle page fault for address:... | 0% Низкий | около 1 года назад | ||
CVE-2023-53642 In the Linux kernel, the following vulnerability has been resolved: x86: fix clear_user_rep_good() exception handling annotation This code no longer exists in mainline, because it was removed in commit d2c95f9d6802 ("x86: don't use REP_GOOD or ERMS for user memory clearing") upstream. However, rather than backport the full range of x86 memory clearing and copying cleanups, fix the exception table annotation placement for the final 'rep movsb' in clear_user_rep_good(): rather than pointing at the actual instruction that did the user space access, it pointed to the register move just before it. That made sense from a code flow standpoint, but not from an actual usage standpoint: it means that if user access takes an exception, the exception handler won't actually find the instruction in the exception tables. As a result, rather than fixing it up and returning -EFAULT, it would then turn it into a kernel oops report instead, something like: BUG: unable to handle page fault for a | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2023-53642 x86: fix clear_user_rep_good() exception handling annotation | 0% Низкий | 9 месяцев назад | ||
CVE-2023-53642 In the Linux kernel, the following vulnerability has been resolved: x ... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
GHSA-h9cf-c7q8-gcqh In the Linux kernel, the following vulnerability has been resolved: x86: fix clear_user_rep_good() exception handling annotation This code no longer exists in mainline, because it was removed in commit d2c95f9d6802 ("x86: don't use REP_GOOD or ERMS for user memory clearing") upstream. However, rather than backport the full range of x86 memory clearing and copying cleanups, fix the exception table annotation placement for the final 'rep movsb' in clear_user_rep_good(): rather than pointing at the actual instruction that did the user space access, it pointed to the register move just before it. That made sense from a code flow standpoint, but not from an actual usage standpoint: it means that if user access takes an exception, the exception handler won't actually find the instruction in the exception tables. As a result, rather than fixing it up and returning -EFAULT, it would then turn it into a kernel oops report instead, something like: BUG: unable to handle page fault fo... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
BDU:2026-03794 Уязвимость функции init_amd() модуля arch/x86/lib/clear_page_64.S ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 3 лет назад | |
ROS-20260826-73-0005 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 3 месяца назад | |
ALT-PU-2023-8798 ALT-PU-2023-8798: package `kernel-image-std-def` update to version 6.1.29-alt1 | CVSS3: 9 | больше 3 лет назад | ||
ALT-PU-2023-8561 ALT-PU-2023-8561: package `kernel-image-un-def` update to version 6.1.29-alt1 | CVSS3: 9 | больше 3 лет назад | ||
ALT-PU-2023-8872 ALT-PU-2023-8872: package `kernel-image-un-def` update to version 6.2.16-alt1 | CVSS3: 9 | больше 3 лет назад | ||
ALT-PU-2023-8723 ALT-PU-2023-8723: package `kernel-image-rt` update to version 6.1.33-alt1.rt11 | CVSS3: 9.8 | больше 3 лет назад | ||
ALT-PU-2023-1826 ALT-PU-2023-1826: package `kernel-image-mp` update to version 6.2.16-alt1 | CVSS3: 9 | больше 3 лет назад | ||
ALT-PU-2023-4663 ALT-PU-2023-4663: package `kernel-image-pine` update to version 6.4.7-alt1 | CVSS3: 9.8 | больше 3 лет назад | ||
ALT-PU-2024-4843 ALT-PU-2024-4843: package `kernel-image-rpi-un` update to version 6.1.77-alt1 | CVSS3: 10 | больше 2 лет назад | ||
ALT-PU-2024-4263 ALT-PU-2024-4263: package `kernel-image-rpi-un` update to version 6.1.77-alt1 | CVSS3: 10 | больше 2 лет назад |
Уязвимостей на страницу