Поиск уязвимостей
Количество 15
Количество 15
CVE-2023-52562
In the Linux kernel, the following vulnerability has been resolved: mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy() After the commit in Fixes:, if a module that created a slab cache does not release all of its allocated objects before destroying the cache (at rmmod time), we might end up releasing the kmem_cache object without removing it from the slab_caches list thus corrupting the list as kmem_cache_destroy() ignores the return value from shutdown_cache(), which in turn never removes the kmem_cache object from slabs_list in case __kmem_cache_shutdown() fails to release all of the cache's slabs. This is easily observable on a kernel built with CONFIG_DEBUG_LIST=y as after that ill release the system will immediately trip on list_add, or list_del, assertions similar to the one shown below as soon as another kmem_cache gets created, or destroyed: [ 1041.213632] list_del corruption. next->prev should be ffff89f596fb5768, but was 52f1e5016aeee75d. (next=ffff...
CVE-2023-52562
In the Linux kernel, the following vulnerability has been resolved: mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy() After the commit in Fixes:, if a module that created a slab cache does not release all of its allocated objects before destroying the cache (at rmmod time), we might end up releasing the kmem_cache object without removing it from the slab_caches list thus corrupting the list as kmem_cache_destroy() ignores the return value from shutdown_cache(), which in turn never removes the kmem_cache object from slabs_list in case __kmem_cache_shutdown() fails to release all of the cache's slabs. This is easily observable on a kernel built with CONFIG_DEBUG_LIST=y as after that ill release the system will immediately trip on list_add, or list_del, assertions similar to the one shown below as soon as another kmem_cache gets created, or destroyed: [ 1041.213632] list_del corruption. next->prev should be ffff89f596fb5768, but was 52f1e5016aeee75d. (next=ffff...
CVE-2023-52562
In the Linux kernel, the following vulnerability has been resolved: mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy() After the commit in Fixes:, if a module that created a slab cache does not release all of its allocated objects before destroying the cache (at rmmod time), we might end up releasing the kmem_cache object without removing it from the slab_caches list thus corrupting the list as kmem_cache_destroy() ignores the return value from shutdown_cache(), which in turn never removes the kmem_cache object from slabs_list in case __kmem_cache_shutdown() fails to release all of the cache's slabs. This is easily observable on a kernel built with CONFIG_DEBUG_LIST=y as after that ill release the system will immediately trip on list_add, or list_del, assertions similar to the one shown below as soon as another kmem_cache gets created, or destroyed: [ 1041.213632] list_del corruption. next->prev should be ffff89f596fb5768, but was 52f1e5016aeee75d. (next=f
CVE-2023-52562
In the Linux kernel, the following vulnerability has been resolved: m ...
GHSA-j56h-xwg2-4wc2
In the Linux kernel, the following vulnerability has been resolved: mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy() After the commit in Fixes:, if a module that created a slab cache does not release all of its allocated objects before destroying the cache (at rmmod time), we might end up releasing the kmem_cache object without removing it from the slab_caches list thus corrupting the list as kmem_cache_destroy() ignores the return value from shutdown_cache(), which in turn never removes the kmem_cache object from slabs_list in case __kmem_cache_shutdown() fails to release all of the cache's slabs. This is easily observable on a kernel built with CONFIG_DEBUG_LIST=y as after that ill release the system will immediately trip on list_add, or list_del, assertions similar to the one shown below as soon as another kmem_cache gets created, or destroyed: [ 1041.213632] list_del corruption. next->prev should be ffff89f596fb5768, but was 52f1e5016aeee75d. (nex...
BDU:2024-01932
Уязвимость функции kmem_cache_destroy библиотеки lib/list_debug.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20240906-02
Множественные уязвимости kernel-lt
ALT-PU-2023-8888
ALT-PU-2023-8888: package `kernel-image-un-def` update to version 6.5.6-alt1
ALT-PU-2023-8819
ALT-PU-2023-8819: package `kernel-image-std-def` update to version 6.1.56-alt1
ALT-PU-2023-8574
ALT-PU-2023-8574: package `kernel-image-un-def` update to version 6.1.57-alt1
ALT-PU-2023-8727
ALT-PU-2023-8727: package `kernel-image-rt` update to version 6.1.59-alt1.rt16
ALT-PU-2023-6505
ALT-PU-2023-6505: package `kernel-image-mp` update to version 6.5.8-alt1
ALT-PU-2023-7004
ALT-PU-2023-7004: package `kernel-image-pine` update to version 6.6.0-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-52562 In the Linux kernel, the following vulnerability has been resolved: mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy() After the commit in Fixes:, if a module that created a slab cache does not release all of its allocated objects before destroying the cache (at rmmod time), we might end up releasing the kmem_cache object without removing it from the slab_caches list thus corrupting the list as kmem_cache_destroy() ignores the return value from shutdown_cache(), which in turn never removes the kmem_cache object from slabs_list in case __kmem_cache_shutdown() fails to release all of the cache's slabs. This is easily observable on a kernel built with CONFIG_DEBUG_LIST=y as after that ill release the system will immediately trip on list_add, or list_del, assertions similar to the one shown below as soon as another kmem_cache gets created, or destroyed: [ 1041.213632] list_del corruption. next->prev should be ffff89f596fb5768, but was 52f1e5016aeee75d. (next=ffff... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2023-52562 In the Linux kernel, the following vulnerability has been resolved: mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy() After the commit in Fixes:, if a module that created a slab cache does not release all of its allocated objects before destroying the cache (at rmmod time), we might end up releasing the kmem_cache object without removing it from the slab_caches list thus corrupting the list as kmem_cache_destroy() ignores the return value from shutdown_cache(), which in turn never removes the kmem_cache object from slabs_list in case __kmem_cache_shutdown() fails to release all of the cache's slabs. This is easily observable on a kernel built with CONFIG_DEBUG_LIST=y as after that ill release the system will immediately trip on list_add, or list_del, assertions similar to the one shown below as soon as another kmem_cache gets created, or destroyed: [ 1041.213632] list_del corruption. next->prev should be ffff89f596fb5768, but was 52f1e5016aeee75d. (next=ffff... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2023-52562 In the Linux kernel, the following vulnerability has been resolved: mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy() After the commit in Fixes:, if a module that created a slab cache does not release all of its allocated objects before destroying the cache (at rmmod time), we might end up releasing the kmem_cache object without removing it from the slab_caches list thus corrupting the list as kmem_cache_destroy() ignores the return value from shutdown_cache(), which in turn never removes the kmem_cache object from slabs_list in case __kmem_cache_shutdown() fails to release all of the cache's slabs. This is easily observable on a kernel built with CONFIG_DEBUG_LIST=y as after that ill release the system will immediately trip on list_add, or list_del, assertions similar to the one shown below as soon as another kmem_cache gets created, or destroyed: [ 1041.213632] list_del corruption. next->prev should be ffff89f596fb5768, but was 52f1e5016aeee75d. (next=f | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2023-52562 In the Linux kernel, the following vulnerability has been resolved: m ... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
GHSA-j56h-xwg2-4wc2 In the Linux kernel, the following vulnerability has been resolved: mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy() After the commit in Fixes:, if a module that created a slab cache does not release all of its allocated objects before destroying the cache (at rmmod time), we might end up releasing the kmem_cache object without removing it from the slab_caches list thus corrupting the list as kmem_cache_destroy() ignores the return value from shutdown_cache(), which in turn never removes the kmem_cache object from slabs_list in case __kmem_cache_shutdown() fails to release all of the cache's slabs. This is easily observable on a kernel built with CONFIG_DEBUG_LIST=y as after that ill release the system will immediately trip on list_add, or list_del, assertions similar to the one shown below as soon as another kmem_cache gets created, or destroyed: [ 1041.213632] list_del corruption. next->prev should be ffff89f596fb5768, but was 52f1e5016aeee75d. (nex... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
BDU:2024-01932 Уязвимость функции kmem_cache_destroy библиотеки lib/list_debug.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | около 3 лет назад | |
ROS-20240906-02 Множественные уязвимости kernel-lt | CVSS3: 5.5 | около 2 лет назад | ||
ALT-PU-2023-8888 ALT-PU-2023-8888: package `kernel-image-un-def` update to version 6.5.6-alt1 | CVSS3: 9.1 | около 3 лет назад | ||
ALT-PU-2023-8819 ALT-PU-2023-8819: package `kernel-image-std-def` update to version 6.1.56-alt1 | CVSS3: 9.1 | около 3 лет назад | ||
ALT-PU-2023-8574 ALT-PU-2023-8574: package `kernel-image-un-def` update to version 6.1.57-alt1 | CVSS3: 9.1 | около 3 лет назад | ||
ALT-PU-2023-8727 ALT-PU-2023-8727: package `kernel-image-rt` update to version 6.1.59-alt1.rt16 | CVSS3: 9.1 | около 3 лет назад | ||
ALT-PU-2023-6505 ALT-PU-2023-6505: package `kernel-image-mp` update to version 6.5.8-alt1 | CVSS3: 9.1 | около 3 лет назад | ||
ALT-PU-2023-7004 ALT-PU-2023-7004: package `kernel-image-pine` update to version 6.6.0-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 лет назад |
Уязвимостей на страницу