Поиск уязвимостей
Количество 22
Количество 22
CVE-2023-52497
In the Linux kernel, the following vulnerability has been resolved: erofs: fix lz4 inplace decompression Currently EROFS can map another compressed buffer for inplace decompression, that was used to handle the cases that some pages of compressed data are actually not in-place I/O. However, like most simple LZ77 algorithms, LZ4 expects the compressed data is arranged at the end of the decompressed buffer and it explicitly uses memmove() to handle overlapping: __________________________________________________________ |_ direction of decompression --> ____ |_ compressed data _| Although EROFS arranges compressed data like this, it typically maps two individual virtual buffers so the relative order is uncertain. Previously, it was hardly observed since LZ4 only uses memmove() for short overlapped literals and x86/arm64 memmove implementations seem to completely cover it up and they don't have this issue. Juhyung reported that EROFS data corruption can be found on a new Intel x86 proce...
CVE-2023-52497
In the Linux kernel, the following vulnerability has been resolved: erofs: fix lz4 inplace decompression Currently EROFS can map another compressed buffer for inplace decompression, that was used to handle the cases that some pages of compressed data are actually not in-place I/O. However, like most simple LZ77 algorithms, LZ4 expects the compressed data is arranged at the end of the decompressed buffer and it explicitly uses memmove() to handle overlapping: __________________________________________________________ |_ direction of decompression --> ____ |_ compressed data _| Although EROFS arranges compressed data like this, it typically maps two individual virtual buffers so the relative order is uncertain. Previously, it was hardly observed since LZ4 only uses memmove() for short overlapped literals and x86/arm64 memmove implementations seem to completely cover it up and they don't have this issue. Juhyung reported that EROFS data corruption can be found on a new Intel x86 proce...
CVE-2023-52497
In the Linux kernel, the following vulnerability has been resolved: erofs: fix lz4 inplace decompression Currently EROFS can map another compressed buffer for inplace decompression, that was used to handle the cases that some pages of compressed data are actually not in-place I/O. However, like most simple LZ77 algorithms, LZ4 expects the compressed data is arranged at the end of the decompressed buffer and it explicitly uses memmove() to handle overlapping: __________________________________________________________ |_ direction of decompression --> ____ |_ compressed data _| Although EROFS arranges compressed data like this, it typically maps two individual virtual buffers so the relative order is uncertain. Previously, it was hardly observed since LZ4 only uses memmove() for short overlapped literals and x86/arm64 memmove implementations seem to completely cover it up and they don't have this issue. Juhyung reported that EROFS data corruption can be found on a new Intel x86 p
CVE-2023-52497
In the Linux kernel, the following vulnerability has been resolved: e ...
GHSA-7hmq-6483-qr84
In the Linux kernel, the following vulnerability has been resolved: erofs: fix lz4 inplace decompression Currently EROFS can map another compressed buffer for inplace decompression, that was used to handle the cases that some pages of compressed data are actually not in-place I/O. However, like most simple LZ77 algorithms, LZ4 expects the compressed data is arranged at the end of the decompressed buffer and it explicitly uses memmove() to handle overlapping: __________________________________________________________ |_ direction of decompression --> ____ |_ compressed data _| Although EROFS arranges compressed data like this, it typically maps two individual virtual buffers so the relative order is uncertain. Previously, it was hardly observed since LZ4 only uses memmove() for short overlapped literals and x86/arm64 memmove implementations seem to completely cover it up and they don't have this issue. Juhyung reported that EROFS data corruption can be found on a new Intel x8...
BDU:2024-07840
Уязвимость компонента erofs ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20241002-06
Множественные уязвимости kernel-lt
ALT-PU-2024-18074
ALT-PU-2024-18074: package `kernel-image-rt` update to version 5.10.211-alt1.rt103
SUSE-SU-2024:1321-1
Security update for the Linux Kernel
ALT-PU-2024-1921
ALT-PU-2024-1921: package `kernel-image-un-def` update to version 6.6.15-alt1
ALT-PU-2024-18204
ALT-PU-2024-18204: package `kernel-image-pine` update to version 6.6.15-alt1
ALT-PU-2024-2015
ALT-PU-2024-2015: package `kernel-image-rt` update to version 6.1.77-alt1.rt24
ALT-PU-2024-1930
ALT-PU-2024-1930: package `kernel-image-un-def` update to version 6.1.77-alt1
ALT-PU-2024-18359
ALT-PU-2024-18359: package `kernel-image-std-def` update to version 6.1.77-alt1
SUSE-SU-2024:1466-1
Security update for the Linux Kernel
SUSE-SU-2024:1322-1
Security update for the Linux Kernel
SUSE-SU-2024:1480-1
Security update for the Linux Kernel
SUSE-SU-2024:1490-1
Security update for the Linux Kernel
ALT-PU-2024-3457
ALT-PU-2024-3457: package `kernel-image-std-def` update to version 5.10.211-alt1
ALT-PU-2024-1865
ALT-PU-2024-1865: package `kernel-image-mp` update to version 6.6.16-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2023-52497 In the Linux kernel, the following vulnerability has been resolved: erofs: fix lz4 inplace decompression Currently EROFS can map another compressed buffer for inplace decompression, that was used to handle the cases that some pages of compressed data are actually not in-place I/O. However, like most simple LZ77 algorithms, LZ4 expects the compressed data is arranged at the end of the decompressed buffer and it explicitly uses memmove() to handle overlapping: __________________________________________________________ |_ direction of decompression --> ____ |_ compressed data _| Although EROFS arranges compressed data like this, it typically maps two individual virtual buffers so the relative order is uncertain. Previously, it was hardly observed since LZ4 only uses memmove() for short overlapped literals and x86/arm64 memmove implementations seem to completely cover it up and they don't have this issue. Juhyung reported that EROFS data corruption can be found on a new Intel x86 proce... | CVSS3: 6.1 | 0% Низкий | больше 2 лет назад | |
CVE-2023-52497 In the Linux kernel, the following vulnerability has been resolved: erofs: fix lz4 inplace decompression Currently EROFS can map another compressed buffer for inplace decompression, that was used to handle the cases that some pages of compressed data are actually not in-place I/O. However, like most simple LZ77 algorithms, LZ4 expects the compressed data is arranged at the end of the decompressed buffer and it explicitly uses memmove() to handle overlapping: __________________________________________________________ |_ direction of decompression --> ____ |_ compressed data _| Although EROFS arranges compressed data like this, it typically maps two individual virtual buffers so the relative order is uncertain. Previously, it was hardly observed since LZ4 only uses memmove() for short overlapped literals and x86/arm64 memmove implementations seem to completely cover it up and they don't have this issue. Juhyung reported that EROFS data corruption can be found on a new Intel x86 proce... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2023-52497 In the Linux kernel, the following vulnerability has been resolved: erofs: fix lz4 inplace decompression Currently EROFS can map another compressed buffer for inplace decompression, that was used to handle the cases that some pages of compressed data are actually not in-place I/O. However, like most simple LZ77 algorithms, LZ4 expects the compressed data is arranged at the end of the decompressed buffer and it explicitly uses memmove() to handle overlapping: __________________________________________________________ |_ direction of decompression --> ____ |_ compressed data _| Although EROFS arranges compressed data like this, it typically maps two individual virtual buffers so the relative order is uncertain. Previously, it was hardly observed since LZ4 only uses memmove() for short overlapped literals and x86/arm64 memmove implementations seem to completely cover it up and they don't have this issue. Juhyung reported that EROFS data corruption can be found on a new Intel x86 p | CVSS3: 6.1 | 0% Низкий | больше 2 лет назад | |
CVE-2023-52497 In the Linux kernel, the following vulnerability has been resolved: e ... | CVSS3: 6.1 | 0% Низкий | больше 2 лет назад | |
GHSA-7hmq-6483-qr84 In the Linux kernel, the following vulnerability has been resolved: erofs: fix lz4 inplace decompression Currently EROFS can map another compressed buffer for inplace decompression, that was used to handle the cases that some pages of compressed data are actually not in-place I/O. However, like most simple LZ77 algorithms, LZ4 expects the compressed data is arranged at the end of the decompressed buffer and it explicitly uses memmove() to handle overlapping: __________________________________________________________ |_ direction of decompression --> ____ |_ compressed data _| Although EROFS arranges compressed data like this, it typically maps two individual virtual buffers so the relative order is uncertain. Previously, it was hardly observed since LZ4 only uses memmove() for short overlapped literals and x86/arm64 memmove implementations seem to completely cover it up and they don't have this issue. Juhyung reported that EROFS data corruption can be found on a new Intel x8... | CVSS3: 6.1 | 0% Низкий | больше 2 лет назад | |
BDU:2024-07840 Уязвимость компонента erofs ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 4.4 | 0% Низкий | почти 3 года назад | |
ROS-20241002-06 Множественные уязвимости kernel-lt | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2024-18074 ALT-PU-2024-18074: package `kernel-image-rt` update to version 5.10.211-alt1.rt103 | CVSS3: 8.8 | больше 2 лет назад | ||
SUSE-SU-2024:1321-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2024-1921 ALT-PU-2024-1921: package `kernel-image-un-def` update to version 6.6.15-alt1 | CVSS3: 9.8 | почти 3 года назад | ||
ALT-PU-2024-18204 ALT-PU-2024-18204: package `kernel-image-pine` update to version 6.6.15-alt1 | CVSS3: 9.8 | почти 3 года назад | ||
ALT-PU-2024-2015 ALT-PU-2024-2015: package `kernel-image-rt` update to version 6.1.77-alt1.rt24 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-1930 ALT-PU-2024-1930: package `kernel-image-un-def` update to version 6.1.77-alt1 | CVSS3: 9.8 | почти 3 года назад | ||
ALT-PU-2024-18359 ALT-PU-2024-18359: package `kernel-image-std-def` update to version 6.1.77-alt1 | CVSS3: 9.8 | почти 3 года назад | ||
SUSE-SU-2024:1466-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:1322-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:1480-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:1490-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2024-3457 ALT-PU-2024-3457: package `kernel-image-std-def` update to version 5.10.211-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-1865 ALT-PU-2024-1865: package `kernel-image-mp` update to version 6.6.16-alt1 | CVSS3: 9.8 | почти 3 года назад |
Уязвимостей на страницу