Поиск уязвимостей
Количество 14
Количество 14
BDU:2026-02037
Уязвимость функции check_func_arg() в модуле kernel/bpf/verifier.c поддержки интерпретатора BPF ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
CVE-2022-49961
In the Linux kernel, the following vulnerability has been resolved: bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO Precision markers need to be propagated whenever we have an ARG_CONST_* style argument, as the verifier cannot consider imprecise scalars to be equivalent for the purposes of states_equal check when such arguments refine the return value (in this case, set mem_size for PTR_TO_MEM). The resultant mem_size for the R0 is derived from the constant value, and if the verifier incorrectly prunes states considering them equivalent where such arguments exist (by seeing that both registers have reg->precise as false in regsafe), we can end up with invalid programs passing the verifier which can do access beyond what should have been the correct mem_size in that explored state. To show a concrete example of the problem: 0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 + 76) 2: r3 = r1 3: r3 += 4 4: if r3 > r2 goto ...
CVE-2022-49961
In the Linux kernel, the following vulnerability has been resolved: bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO Precision markers need to be propagated whenever we have an ARG_CONST_* style argument, as the verifier cannot consider imprecise scalars to be equivalent for the purposes of states_equal check when such arguments refine the return value (in this case, set mem_size for PTR_TO_MEM). The resultant mem_size for the R0 is derived from the constant value, and if the verifier incorrectly prunes states considering them equivalent where such arguments exist (by seeing that both registers have reg->precise as false in regsafe), we can end up with invalid programs passing the verifier which can do access beyond what should have been the correct mem_size in that explored state. To show a concrete example of the problem: 0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 + 76) 2: r3 = r1 3: r3 += 4 4: if r3 > r2 goto ...
CVE-2022-49961
In the Linux kernel, the following vulnerability has been resolved: bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO Precision markers need to be propagated whenever we have an ARG_CONST_* style argument, as the verifier cannot consider imprecise scalars to be equivalent for the purposes of states_equal check when such arguments refine the return value (in this case, set mem_size for PTR_TO_MEM). The resultant mem_size for the R0 is derived from the constant value, and if the verifier incorrectly prunes states considering them equivalent where such arguments exist (by seeing that both registers have reg->precise as false in regsafe), we can end up with invalid programs passing the verifier which can do access beyond what should have been the correct mem_size in that explored state. To show a concrete example of the problem: 0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 + 76) 2: r3 = r1 3: r3 +
CVE-2022-49961
bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO
CVE-2022-49961
In the Linux kernel, the following vulnerability has been resolved: b ...
GHSA-34r5-4vr6-q5h6
In the Linux kernel, the following vulnerability has been resolved: bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO Precision markers need to be propagated whenever we have an ARG_CONST_* style argument, as the verifier cannot consider imprecise scalars to be equivalent for the purposes of states_equal check when such arguments refine the return value (in this case, set mem_size for PTR_TO_MEM). The resultant mem_size for the R0 is derived from the constant value, and if the verifier incorrectly prunes states considering them equivalent where such arguments exist (by seeing that both registers have reg->precise as false in regsafe), we can end up with invalid programs passing the verifier which can do access beyond what should have been the correct mem_size in that explored state. To show a concrete example of the problem: 0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 + 76) 2: r3 = r1 3: r...
ALT-PU-2022-2586
ALT-PU-2022-2586: package `kernel-image-un-def` update to version 5.19.8-alt1
ALT-PU-2022-2594
ALT-PU-2022-2594: package `kernel-image-mp` update to version 5.19.8-alt1
ALT-PU-2023-1741
ALT-PU-2023-1741: package `kernel-image-un-def` update to version 6.1.26-alt1
ALT-PU-2023-1684
ALT-PU-2023-1684: package `kernel-image-std-def` update to version 6.1.26-alt1
ALT-PU-2022-2919
ALT-PU-2022-2919: package `kernel-image-rpi-un` update to version 6.0.2-alt1
ALT-PU-2022-2915
ALT-PU-2022-2915: package `kernel-image-rpi-un` update to version 6.0.2-alt1
ALT-PU-2023-1814
ALT-PU-2023-1814: package `kernel-image-rt` update to version 6.1.28-alt1.rt10
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
BDU:2026-02037 Уязвимость функции check_func_arg() в модуле kernel/bpf/verifier.c поддержки интерпретатора BPF ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации | CVSS3: 8 | 0% Низкий | около 4 лет назад | |
CVE-2022-49961 In the Linux kernel, the following vulnerability has been resolved: bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO Precision markers need to be propagated whenever we have an ARG_CONST_* style argument, as the verifier cannot consider imprecise scalars to be equivalent for the purposes of states_equal check when such arguments refine the return value (in this case, set mem_size for PTR_TO_MEM). The resultant mem_size for the R0 is derived from the constant value, and if the verifier incorrectly prunes states considering them equivalent where such arguments exist (by seeing that both registers have reg->precise as false in regsafe), we can end up with invalid programs passing the verifier which can do access beyond what should have been the correct mem_size in that explored state. To show a concrete example of the problem: 0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 + 76) 2: r3 = r1 3: r3 += 4 4: if r3 > r2 goto ... | CVSS3: 7.1 | 0% Низкий | больше 1 года назад | |
CVE-2022-49961 In the Linux kernel, the following vulnerability has been resolved: bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO Precision markers need to be propagated whenever we have an ARG_CONST_* style argument, as the verifier cannot consider imprecise scalars to be equivalent for the purposes of states_equal check when such arguments refine the return value (in this case, set mem_size for PTR_TO_MEM). The resultant mem_size for the R0 is derived from the constant value, and if the verifier incorrectly prunes states considering them equivalent where such arguments exist (by seeing that both registers have reg->precise as false in regsafe), we can end up with invalid programs passing the verifier which can do access beyond what should have been the correct mem_size in that explored state. To show a concrete example of the problem: 0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 + 76) 2: r3 = r1 3: r3 += 4 4: if r3 > r2 goto ... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2022-49961 In the Linux kernel, the following vulnerability has been resolved: bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO Precision markers need to be propagated whenever we have an ARG_CONST_* style argument, as the verifier cannot consider imprecise scalars to be equivalent for the purposes of states_equal check when such arguments refine the return value (in this case, set mem_size for PTR_TO_MEM). The resultant mem_size for the R0 is derived from the constant value, and if the verifier incorrectly prunes states considering them equivalent where such arguments exist (by seeing that both registers have reg->precise as false in regsafe), we can end up with invalid programs passing the verifier which can do access beyond what should have been the correct mem_size in that explored state. To show a concrete example of the problem: 0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 + 76) 2: r3 = r1 3: r3 + | CVSS3: 7.1 | 0% Низкий | больше 1 года назад | |
CVE-2022-49961 bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO | CVSS3: 6 | 0% Низкий | около 1 года назад | |
CVE-2022-49961 In the Linux kernel, the following vulnerability has been resolved: b ... | CVSS3: 7.1 | 0% Низкий | больше 1 года назад | |
GHSA-34r5-4vr6-q5h6 In the Linux kernel, the following vulnerability has been resolved: bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO Precision markers need to be propagated whenever we have an ARG_CONST_* style argument, as the verifier cannot consider imprecise scalars to be equivalent for the purposes of states_equal check when such arguments refine the return value (in this case, set mem_size for PTR_TO_MEM). The resultant mem_size for the R0 is derived from the constant value, and if the verifier incorrectly prunes states considering them equivalent where such arguments exist (by seeing that both registers have reg->precise as false in regsafe), we can end up with invalid programs passing the verifier which can do access beyond what should have been the correct mem_size in that explored state. To show a concrete example of the problem: 0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 + 80) 1: r1 = *(u32 *)(r1 + 76) 2: r3 = r1 3: r... | CVSS3: 7.1 | 0% Низкий | больше 1 года назад | |
ALT-PU-2022-2586 ALT-PU-2022-2586: package `kernel-image-un-def` update to version 5.19.8-alt1 | CVSS3: 8 | около 4 лет назад | ||
ALT-PU-2022-2594 ALT-PU-2022-2594: package `kernel-image-mp` update to version 5.19.8-alt1 | CVSS3: 8 | около 4 лет назад | ||
ALT-PU-2023-1741 ALT-PU-2023-1741: package `kernel-image-un-def` update to version 6.1.26-alt1 | CVSS3: 9.8 | больше 3 лет назад | ||
ALT-PU-2023-1684 ALT-PU-2023-1684: package `kernel-image-std-def` update to version 6.1.26-alt1 | CVSS3: 9.8 | больше 3 лет назад | ||
ALT-PU-2022-2919 ALT-PU-2022-2919: package `kernel-image-rpi-un` update to version 6.0.2-alt1 | CVSS3: 10 | около 4 лет назад | ||
ALT-PU-2022-2915 ALT-PU-2022-2915: package `kernel-image-rpi-un` update to version 6.0.2-alt1 | CVSS3: 10 | около 4 лет назад | ||
ALT-PU-2023-1814 ALT-PU-2023-1814: package `kernel-image-rt` update to version 6.1.28-alt1.rt10 | CVSS3: 9.8 | больше 3 лет назад |
Уязвимостей на страницу