Поиск уязвимостей
Количество 15
Количество 15
BDU:2026-02031
Уязвимость функции dma_resv_add_fence() в модуле drivers/dma-buf/dma-resv.c 2 ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
CVE-2022-49935
In the Linux kernel, the following vulnerability has been resolved: dma-buf/dma-resv: check if the new fence is really later Previously when we added a fence to a dma_resv object we always assumed the the newer than all the existing fences. With Jason's work to add an UAPI to explicit export/import that's not necessary the case any more. So without this check we would allow userspace to force the kernel into an use after free error. Since the change is very small and defensive it's probably a good idea to backport this to stable kernels as well just in case others are using the dma_resv object in the same way.
CVE-2022-49935
In the Linux kernel, the following vulnerability has been resolved: dma-buf/dma-resv: check if the new fence is really later Previously when we added a fence to a dma_resv object we always assumed the the newer than all the existing fences. With Jason's work to add an UAPI to explicit export/import that's not necessary the case any more. So without this check we would allow userspace to force the kernel into an use after free error. Since the change is very small and defensive it's probably a good idea to backport this to stable kernels as well just in case others are using the dma_resv object in the same way.
CVE-2022-49935
In the Linux kernel, the following vulnerability has been resolved: dma-buf/dma-resv: check if the new fence is really later Previously when we added a fence to a dma_resv object we always assumed the the newer than all the existing fences. With Jason's work to add an UAPI to explicit export/import that's not necessary the case any more. So without this check we would allow userspace to force the kernel into an use after free error. Since the change is very small and defensive it's probably a good idea to backport this to stable kernels as well just in case others are using the dma_resv object in the same way.
CVE-2022-49935
dma-buf/dma-resv: check if the new fence is really later
CVE-2022-49935
In the Linux kernel, the following vulnerability has been resolved: d ...
GHSA-rj36-vf3r-744c
In the Linux kernel, the following vulnerability has been resolved: dma-buf/dma-resv: check if the new fence is really later Previously when we added a fence to a dma_resv object we always assumed the the newer than all the existing fences. With Jason's work to add an UAPI to explicit export/import that's not necessary the case any more. So without this check we would allow userspace to force the kernel into an use after free error. Since the change is very small and defensive it's probably a good idea to backport this to stable kernels as well just in case others are using the dma_resv object in the same way.
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
SUSE-SU-2025:02264-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
BDU:2026-02031 Уязвимость функции dma_resv_add_fence() в модуле drivers/dma-buf/dma-resv.c 2 ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации | CVSS3: 8 | 0% Низкий | около 4 лет назад | |
CVE-2022-49935 In the Linux kernel, the following vulnerability has been resolved: dma-buf/dma-resv: check if the new fence is really later Previously when we added a fence to a dma_resv object we always assumed the the newer than all the existing fences. With Jason's work to add an UAPI to explicit export/import that's not necessary the case any more. So without this check we would allow userspace to force the kernel into an use after free error. Since the change is very small and defensive it's probably a good idea to backport this to stable kernels as well just in case others are using the dma_resv object in the same way. | CVSS3: 7.8 | 0% Низкий | больше 1 года назад | |
CVE-2022-49935 In the Linux kernel, the following vulnerability has been resolved: dma-buf/dma-resv: check if the new fence is really later Previously when we added a fence to a dma_resv object we always assumed the the newer than all the existing fences. With Jason's work to add an UAPI to explicit export/import that's not necessary the case any more. So without this check we would allow userspace to force the kernel into an use after free error. Since the change is very small and defensive it's probably a good idea to backport this to stable kernels as well just in case others are using the dma_resv object in the same way. | CVSS3: 7 | 0% Низкий | больше 1 года назад | |
CVE-2022-49935 In the Linux kernel, the following vulnerability has been resolved: dma-buf/dma-resv: check if the new fence is really later Previously when we added a fence to a dma_resv object we always assumed the the newer than all the existing fences. With Jason's work to add an UAPI to explicit export/import that's not necessary the case any more. So without this check we would allow userspace to force the kernel into an use after free error. Since the change is very small and defensive it's probably a good idea to backport this to stable kernels as well just in case others are using the dma_resv object in the same way. | CVSS3: 7.8 | 0% Низкий | больше 1 года назад | |
CVE-2022-49935 dma-buf/dma-resv: check if the new fence is really later | CVSS3: 7 | 0% Низкий | около 1 года назад | |
CVE-2022-49935 In the Linux kernel, the following vulnerability has been resolved: d ... | CVSS3: 7.8 | 0% Низкий | больше 1 года назад | |
GHSA-rj36-vf3r-744c In the Linux kernel, the following vulnerability has been resolved: dma-buf/dma-resv: check if the new fence is really later Previously when we added a fence to a dma_resv object we always assumed the the newer than all the existing fences. With Jason's work to add an UAPI to explicit export/import that's not necessary the case any more. So without this check we would allow userspace to force the kernel into an use after free error. Since the change is very small and defensive it's probably a good idea to backport this to stable kernels as well just in case others are using the dma_resv object in the same way. | CVSS3: 7.8 | 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 лет назад | ||
SUSE-SU-2025:02264-1 Security update for the Linux Kernel | больше 1 года назад |
Уязвимостей на страницу