Поиск уязвимостей
Количество 19
Количество 19
GHSA-72rq-7p7f-9f9j
In the Linux kernel, the following vulnerability has been resolved: erofs: Fix detection of atomic context Current check for atomic context is not sufficient as z_erofs_decompressqueue_endio can be called under rcu lock from blk_mq_flush_plug_list(). See the stacktrace [1] In such case we should hand off the decompression work for async processing rather than trying to do sync decompression in current context. Patch fixes the detection by checking for rcu_read_lock_any_held() and while at it use more appropriate !in_task() check than in_atomic(). Background: Historically erofs would always schedule a kworker for decompression which would incur the scheduling cost regardless of the context. But z_erofs_decompressqueue_endio() may not always be in atomic context and we could actually benefit from doing the decompression in z_erofs_decompressqueue_endio() if we are in thread context, for example when running with dm-verity. This optimization was later added in patch [2] which has s...
CVE-2023-53231
In the Linux kernel, the following vulnerability has been resolved: erofs: Fix detection of atomic context Current check for atomic context is not sufficient as z_erofs_decompressqueue_endio can be called under rcu lock from blk_mq_flush_plug_list(). See the stacktrace [1] In such case we should hand off the decompression work for async processing rather than trying to do sync decompression in current context. Patch fixes the detection by checking for rcu_read_lock_any_held() and while at it use more appropriate !in_task() check than in_atomic(). Background: Historically erofs would always schedule a kworker for decompression which would incur the scheduling cost regardless of the context. But z_erofs_decompressqueue_endio() may not always be in atomic context and we could actually benefit from doing the decompression in z_erofs_decompressqueue_endio() if we are in thread context, for example when running with dm-verity. This optimization was later added in patch [2] which has shown...
CVE-2023-53231
In the Linux kernel, the following vulnerability has been resolved: erofs: Fix detection of atomic context Current check for atomic context is not sufficient as z_erofs_decompressqueue_endio can be called under rcu lock from blk_mq_flush_plug_list(). See the stacktrace [1] In such case we should hand off the decompression work for async processing rather than trying to do sync decompression in current context. Patch fixes the detection by checking for rcu_read_lock_any_held() and while at it use more appropriate !in_task() check than in_atomic(). Background: Historically erofs would always schedule a kworker for decompression which would incur the scheduling cost regardless of the context. But z_erofs_decompressqueue_endio() may not always be in atomic context and we could actually benefit from doing the decompression in z_erofs_decompressqueue_endio() if we are in thread context, for example when running with dm-verity. This optimization was later added in patch [2] which has shown...
CVE-2023-53231
In the Linux kernel, the following vulnerability has been resolved: erofs: Fix detection of atomic context Current check for atomic context is not sufficient as z_erofs_decompressqueue_endio can be called under rcu lock from blk_mq_flush_plug_list(). See the stacktrace [1] In such case we should hand off the decompression work for async processing rather than trying to do sync decompression in current context. Patch fixes the detection by checking for rcu_read_lock_any_held() and while at it use more appropriate !in_task() check than in_atomic(). Background: Historically erofs would always schedule a kworker for decompression which would incur the scheduling cost regardless of the context. But z_erofs_decompressqueue_endio() may not always be in atomic context and we could actually benefit from doing the decompression in z_erofs_decompressqueue_endio() if we are in thread context, for example when running with dm-verity. This optimization was later added in patch [2] which has show
CVE-2023-53231
erofs: Fix detection of atomic context
CVE-2023-53231
In the Linux kernel, the following vulnerability has been resolved: e ...
BDU:2026-08830
Уязвимость функции z_erofs_decompress_kickoff() модуля fs/erofs/zdata.c файловой системы EROFS (Enhanced ReadOnly File System) ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20261112-73-0066
Уязвимость kernel-lt
ALT-PU-2023-8881
ALT-PU-2023-8881: package `kernel-image-un-def` update to version 6.4.7-alt1
ALT-PU-2023-8659
ALT-PU-2023-8659: package `kernel-image-mp` update to version 6.4.8-alt1
SUSE-SU-2025:3751-1
Security update for the Linux Kernel
SUSE-SU-2025:03600-1
Security update for the Linux Kernel
SUSE-SU-2025:03634-1
Security update for the Linux Kernel
SUSE-SU-2025:4141-1
Security update for the Linux Kernel
SUSE-SU-2025:4132-1
Security update for the Linux Kernel
SUSE-SU-2025:4057-1
Security update for the Linux Kernel
ALT-PU-2023-4663
ALT-PU-2023-4663: package `kernel-image-pine` update to version 6.4.7-alt1
ALT-PU-2024-6818
ALT-PU-2024-6818: package `kernel-image-rpi-un` update to version 6.6.23-alt1
ALT-PU-2024-14046
ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
GHSA-72rq-7p7f-9f9j In the Linux kernel, the following vulnerability has been resolved: erofs: Fix detection of atomic context Current check for atomic context is not sufficient as z_erofs_decompressqueue_endio can be called under rcu lock from blk_mq_flush_plug_list(). See the stacktrace [1] In such case we should hand off the decompression work for async processing rather than trying to do sync decompression in current context. Patch fixes the detection by checking for rcu_read_lock_any_held() and while at it use more appropriate !in_task() check than in_atomic(). Background: Historically erofs would always schedule a kworker for decompression which would incur the scheduling cost regardless of the context. But z_erofs_decompressqueue_endio() may not always be in atomic context and we could actually benefit from doing the decompression in z_erofs_decompressqueue_endio() if we are in thread context, for example when running with dm-verity. This optimization was later added in patch [2] which has s... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2023-53231 In the Linux kernel, the following vulnerability has been resolved: erofs: Fix detection of atomic context Current check for atomic context is not sufficient as z_erofs_decompressqueue_endio can be called under rcu lock from blk_mq_flush_plug_list(). See the stacktrace [1] In such case we should hand off the decompression work for async processing rather than trying to do sync decompression in current context. Patch fixes the detection by checking for rcu_read_lock_any_held() and while at it use more appropriate !in_task() check than in_atomic(). Background: Historically erofs would always schedule a kworker for decompression which would incur the scheduling cost regardless of the context. But z_erofs_decompressqueue_endio() may not always be in atomic context and we could actually benefit from doing the decompression in z_erofs_decompressqueue_endio() if we are in thread context, for example when running with dm-verity. This optimization was later added in patch [2] which has shown... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2023-53231 In the Linux kernel, the following vulnerability has been resolved: erofs: Fix detection of atomic context Current check for atomic context is not sufficient as z_erofs_decompressqueue_endio can be called under rcu lock from blk_mq_flush_plug_list(). See the stacktrace [1] In such case we should hand off the decompression work for async processing rather than trying to do sync decompression in current context. Patch fixes the detection by checking for rcu_read_lock_any_held() and while at it use more appropriate !in_task() check than in_atomic(). Background: Historically erofs would always schedule a kworker for decompression which would incur the scheduling cost regardless of the context. But z_erofs_decompressqueue_endio() may not always be in atomic context and we could actually benefit from doing the decompression in z_erofs_decompressqueue_endio() if we are in thread context, for example when running with dm-verity. This optimization was later added in patch [2] which has shown... | 0% Низкий | около 1 года назад | ||
CVE-2023-53231 In the Linux kernel, the following vulnerability has been resolved: erofs: Fix detection of atomic context Current check for atomic context is not sufficient as z_erofs_decompressqueue_endio can be called under rcu lock from blk_mq_flush_plug_list(). See the stacktrace [1] In such case we should hand off the decompression work for async processing rather than trying to do sync decompression in current context. Patch fixes the detection by checking for rcu_read_lock_any_held() and while at it use more appropriate !in_task() check than in_atomic(). Background: Historically erofs would always schedule a kworker for decompression which would incur the scheduling cost regardless of the context. But z_erofs_decompressqueue_endio() may not always be in atomic context and we could actually benefit from doing the decompression in z_erofs_decompressqueue_endio() if we are in thread context, for example when running with dm-verity. This optimization was later added in patch [2] which has show | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2023-53231 erofs: Fix detection of atomic context | 0% Низкий | 12 месяцев назад | ||
CVE-2023-53231 In the Linux kernel, the following vulnerability has been resolved: e ... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
BDU:2026-08830 Уязвимость функции z_erofs_decompress_kickoff() модуля fs/erofs/zdata.c файловой системы EROFS (Enhanced ReadOnly File System) ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 3 лет назад | |
ROS-20261112-73-0066 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 10 дней назад | |
ALT-PU-2023-8881 ALT-PU-2023-8881: package `kernel-image-un-def` update to version 6.4.7-alt1 | CVSS3: 8 | больше 3 лет назад | ||
ALT-PU-2023-8659 ALT-PU-2023-8659: package `kernel-image-mp` update to version 6.4.8-alt1 | CVSS3: 8.8 | больше 3 лет назад | ||
SUSE-SU-2025:3751-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03600-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03634-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:4141-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:4132-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:4057-1 Security update for the Linux Kernel | около 1 года назад | |||
ALT-PU-2023-4663 ALT-PU-2023-4663: package `kernel-image-pine` update to version 6.4.7-alt1 | CVSS3: 9.8 | больше 3 лет назад | ||
ALT-PU-2024-6818 ALT-PU-2024-6818: package `kernel-image-rpi-un` update to version 6.6.23-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-14046 ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1 | CVSS3: 9.8 | около 2 лет назад |
Уязвимостей на страницу