Поиск уязвимостей
Количество 26
Количество 26
BDU:2024-08412
Уязвимость компонента crypto ядра операционной системы Linux, позволяющая нарушителю получить несанкционированный доступ к конфиденциальной информации
CVE-2022-48629
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - ensure buffer for generate is completely filled The generate function in struct rng_alg expects that the destination buffer is completely filled if the function returns 0. qcom_rng_read() can run into a situation where the buffer is partially filled with randomness and the remaining part of the buffer is zeroed since qcom_rng_generate() doesn't check the return value. This issue can be reproduced by running the following from libkcapi: kcapi-rng -b 9000000 > OUTFILE The generated OUTFILE will have three huge sections that contain all zeros, and this is caused by the code where the test 'val & PRNG_STATUS_DATA_AVAIL' fails. Let's fix this issue by ensuring that qcom_rng_read() always returns with a full buffer if the function returns success. Let's also have qcom_rng_generate() return the correct value. Here's some statistics from the ent project (https://www.fourmilab.ch/random/) that shows inform...
CVE-2022-48629
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - ensure buffer for generate is completely filled The generate function in struct rng_alg expects that the destination buffer is completely filled if the function returns 0. qcom_rng_read() can run into a situation where the buffer is partially filled with randomness and the remaining part of the buffer is zeroed since qcom_rng_generate() doesn't check the return value. This issue can be reproduced by running the following from libkcapi: kcapi-rng -b 9000000 > OUTFILE The generated OUTFILE will have three huge sections that contain all zeros, and this is caused by the code where the test 'val & PRNG_STATUS_DATA_AVAIL' fails. Let's fix this issue by ensuring that qcom_rng_read() always returns with a full buffer if the function returns success. Let's also have qcom_rng_generate() return the correct value. Here's some statistics from the ent project (https://www.fourmilab.ch/random/) that shows inform...
CVE-2022-48629
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - ensure buffer for generate is completely filled The generate function in struct rng_alg expects that the destination buffer is completely filled if the function returns 0. qcom_rng_read() can run into a situation where the buffer is partially filled with randomness and the remaining part of the buffer is zeroed since qcom_rng_generate() doesn't check the return value. This issue can be reproduced by running the following from libkcapi: kcapi-rng -b 9000000 > OUTFILE The generated OUTFILE will have three huge sections that contain all zeros, and this is caused by the code where the test 'val & PRNG_STATUS_DATA_AVAIL' fails. Let's fix this issue by ensuring that qcom_rng_read() always returns with a full buffer if the function returns success. Let's also have qcom_rng_generate() return the correct value. Here's some statistics from the ent project (https://www.fourmilab.ch/random/) that shows
CVE-2022-48629
In the Linux kernel, the following vulnerability has been resolved: c ...
ALT-PU-2022-7800
ALT-PU-2022-7800: package `kernel-image-std-def` update to version 5.15.31-alt1
ALT-PU-2022-1558
ALT-PU-2022-1558: package `kernel-image-un-def` update to version 5.16.17-alt1
GHSA-2689-83hc-5vvp
In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - ensure buffer for generate is completely filled The generate function in struct rng_alg expects that the destination buffer is completely filled if the function returns 0. qcom_rng_read() can run into a situation where the buffer is partially filled with randomness and the remaining part of the buffer is zeroed since qcom_rng_generate() doesn't check the return value. This issue can be reproduced by running the following from libkcapi: kcapi-rng -b 9000000 > OUTFILE The generated OUTFILE will have three huge sections that contain all zeros, and this is caused by the code where the test 'val & PRNG_STATUS_DATA_AVAIL' fails. Let's fix this issue by ensuring that qcom_rng_read() always returns with a full buffer if the function returns success. Let's also have qcom_rng_generate() return the correct value. Here's some statistics from the ent project (https://www.fourmilab.ch/random/) that sh...
ALT-PU-2022-7773
ALT-PU-2022-7773: package `kernel-image-rt` update to version 5.10.109-alt1.rt65
ALT-PU-2022-1659
ALT-PU-2022-1659: package `kernel-image-rt` update to version 5.10.109-alt1.rt65
ROS-20241011-01
Множественные уязвимости kernel-lt
ALT-PU-2022-1630
ALT-PU-2022-1630: package `kernel-image-std-kvm` update to version 5.10.109-alt1
ALT-PU-2022-1611
ALT-PU-2022-1611: package `kernel-image-std-def` update to version 5.10.109-alt1
ALT-PU-2022-1633
ALT-PU-2022-1633: package `kernel-image-un-def` update to version 5.15.32-alt1
ALT-PU-2022-7823
ALT-PU-2022-7823: package `kernel-image-xenomai` update to version 4.19.246-alt1.cip75.22
ALT-PU-2022-1647
ALT-PU-2022-1647: package `kernel-image-rpi-un` update to version 5.17.1-alt1
ALT-PU-2022-1746
ALT-PU-2022-1746: package `kernel-image-rpi-def` update to version 5.15.33-alt1
ALT-PU-2022-2344
ALT-PU-2022-2344: package `kernel-image-xenomai` update to version 4.19.252-alt1.cip78.23
ALT-PU-2022-1730
ALT-PU-2022-1730: package `kernel-image-mp` update to version 5.17.4-alt1
ALT-PU-2022-1833
ALT-PU-2022-1833: package `kernel-image-rpi-def` update to version 5.15.36-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
BDU:2024-08412 Уязвимость компонента crypto ядра операционной системы Linux, позволяющая нарушителю получить несанкционированный доступ к конфиденциальной информации | CVSS3: 5.5 | 1% Низкий | больше 4 лет назад | |
CVE-2022-48629 In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - ensure buffer for generate is completely filled The generate function in struct rng_alg expects that the destination buffer is completely filled if the function returns 0. qcom_rng_read() can run into a situation where the buffer is partially filled with randomness and the remaining part of the buffer is zeroed since qcom_rng_generate() doesn't check the return value. This issue can be reproduced by running the following from libkcapi: kcapi-rng -b 9000000 > OUTFILE The generated OUTFILE will have three huge sections that contain all zeros, and this is caused by the code where the test 'val & PRNG_STATUS_DATA_AVAIL' fails. Let's fix this issue by ensuring that qcom_rng_read() always returns with a full buffer if the function returns success. Let's also have qcom_rng_generate() return the correct value. Here's some statistics from the ent project (https://www.fourmilab.ch/random/) that shows inform... | CVSS3: 5.5 | 1% Низкий | больше 2 лет назад | |
CVE-2022-48629 In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - ensure buffer for generate is completely filled The generate function in struct rng_alg expects that the destination buffer is completely filled if the function returns 0. qcom_rng_read() can run into a situation where the buffer is partially filled with randomness and the remaining part of the buffer is zeroed since qcom_rng_generate() doesn't check the return value. This issue can be reproduced by running the following from libkcapi: kcapi-rng -b 9000000 > OUTFILE The generated OUTFILE will have three huge sections that contain all zeros, and this is caused by the code where the test 'val & PRNG_STATUS_DATA_AVAIL' fails. Let's fix this issue by ensuring that qcom_rng_read() always returns with a full buffer if the function returns success. Let's also have qcom_rng_generate() return the correct value. Here's some statistics from the ent project (https://www.fourmilab.ch/random/) that shows inform... | CVSS3: 5.5 | 1% Низкий | больше 2 лет назад | |
CVE-2022-48629 In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - ensure buffer for generate is completely filled The generate function in struct rng_alg expects that the destination buffer is completely filled if the function returns 0. qcom_rng_read() can run into a situation where the buffer is partially filled with randomness and the remaining part of the buffer is zeroed since qcom_rng_generate() doesn't check the return value. This issue can be reproduced by running the following from libkcapi: kcapi-rng -b 9000000 > OUTFILE The generated OUTFILE will have three huge sections that contain all zeros, and this is caused by the code where the test 'val & PRNG_STATUS_DATA_AVAIL' fails. Let's fix this issue by ensuring that qcom_rng_read() always returns with a full buffer if the function returns success. Let's also have qcom_rng_generate() return the correct value. Here's some statistics from the ent project (https://www.fourmilab.ch/random/) that shows | CVSS3: 5.5 | 1% Низкий | больше 2 лет назад | |
CVE-2022-48629 In the Linux kernel, the following vulnerability has been resolved: c ... | CVSS3: 5.5 | 1% Низкий | больше 2 лет назад | |
ALT-PU-2022-7800 ALT-PU-2022-7800: package `kernel-image-std-def` update to version 5.15.31-alt1 | CVSS3: 7.8 | больше 4 лет назад | ||
ALT-PU-2022-1558 ALT-PU-2022-1558: package `kernel-image-un-def` update to version 5.16.17-alt1 | CVSS3: 7.8 | больше 4 лет назад | ||
GHSA-2689-83hc-5vvp In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - ensure buffer for generate is completely filled The generate function in struct rng_alg expects that the destination buffer is completely filled if the function returns 0. qcom_rng_read() can run into a situation where the buffer is partially filled with randomness and the remaining part of the buffer is zeroed since qcom_rng_generate() doesn't check the return value. This issue can be reproduced by running the following from libkcapi: kcapi-rng -b 9000000 > OUTFILE The generated OUTFILE will have three huge sections that contain all zeros, and this is caused by the code where the test 'val & PRNG_STATUS_DATA_AVAIL' fails. Let's fix this issue by ensuring that qcom_rng_read() always returns with a full buffer if the function returns success. Let's also have qcom_rng_generate() return the correct value. Here's some statistics from the ent project (https://www.fourmilab.ch/random/) that sh... | CVSS3: 5.5 | 1% Низкий | больше 2 лет назад | |
ALT-PU-2022-7773 ALT-PU-2022-7773: package `kernel-image-rt` update to version 5.10.109-alt1.rt65 | CVSS3: 7.8 | больше 4 лет назад | ||
ALT-PU-2022-1659 ALT-PU-2022-1659: package `kernel-image-rt` update to version 5.10.109-alt1.rt65 | CVSS3: 7.8 | больше 4 лет назад | ||
ROS-20241011-01 Множественные уязвимости kernel-lt | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2022-1630 ALT-PU-2022-1630: package `kernel-image-std-kvm` update to version 5.10.109-alt1 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-1611 ALT-PU-2022-1611: package `kernel-image-std-def` update to version 5.10.109-alt1 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-1633 ALT-PU-2022-1633: package `kernel-image-un-def` update to version 5.15.32-alt1 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-7823 ALT-PU-2022-7823: package `kernel-image-xenomai` update to version 4.19.246-alt1.cip75.22 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-1647 ALT-PU-2022-1647: package `kernel-image-rpi-un` update to version 5.17.1-alt1 | CVSS3: 8.4 | больше 4 лет назад | ||
ALT-PU-2022-1746 ALT-PU-2022-1746: package `kernel-image-rpi-def` update to version 5.15.33-alt1 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-2344 ALT-PU-2022-2344: package `kernel-image-xenomai` update to version 4.19.252-alt1.cip78.23 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-1730 ALT-PU-2022-1730: package `kernel-image-mp` update to version 5.17.4-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-1833 ALT-PU-2022-1833: package `kernel-image-rpi-def` update to version 5.15.36-alt1 | CVSS3: 9.8 | больше 4 лет назад |
Уязвимостей на страницу