Поиск уязвимостей
Количество 20
Количество 20
CVE-2022-49761
In the Linux kernel, the following vulnerability has been resolved: btrfs: always report error in run_one_delayed_ref() Currently we have a btrfs_debug() for run_one_delayed_ref() failure, but if end users hit such problem, there will be no chance that btrfs_debug() is enabled. This can lead to very little useful info for debugging. This patch will: - Add extra info for error reporting Including: * logical bytenr * num_bytes * type * action * ref_mod - Replace the btrfs_debug() with btrfs_err() - Move the error reporting into run_one_delayed_ref() This is to avoid use-after-free, the @node can be freed in the caller. This error should only be triggered at most once. As if run_one_delayed_ref() failed, we trigger the error message, then causing the call chain to error out: btrfs_run_delayed_refs() `- btrfs_run_delayed_refs() `- btrfs_run_delayed_refs_for_head() `- run_one_delayed_ref() And we will abort the current transaction in btrfs_run_delayed_refs(). If we have to run delayed r...
CVE-2022-49761
In the Linux kernel, the following vulnerability has been resolved: btrfs: always report error in run_one_delayed_ref() Currently we have a btrfs_debug() for run_one_delayed_ref() failure, but if end users hit such problem, there will be no chance that btrfs_debug() is enabled. This can lead to very little useful info for debugging. This patch will: - Add extra info for error reporting Including: * logical bytenr * num_bytes * type * action * ref_mod - Replace the btrfs_debug() with btrfs_err() - Move the error reporting into run_one_delayed_ref() This is to avoid use-after-free, the @node can be freed in the caller. This error should only be triggered at most once. As if run_one_delayed_ref() failed, we trigger the error message, then causing the call chain to error out: btrfs_run_delayed_refs() `- btrfs_run_delayed_refs() `- btrfs_run_delayed_refs_for_head() `- run_one_delayed_ref() And we will abort the current transaction in btrfs_run_delayed_refs(). If we have to run delayed r...
CVE-2022-49761
In the Linux kernel, the following vulnerability has been resolved: btrfs: always report error in run_one_delayed_ref() Currently we have a btrfs_debug() for run_one_delayed_ref() failure, but if end users hit such problem, there will be no chance that btrfs_debug() is enabled. This can lead to very little useful info for debugging. This patch will: - Add extra info for error reporting Including: * logical bytenr * num_bytes * type * action * ref_mod - Replace the btrfs_debug() with btrfs_err() - Move the error reporting into run_one_delayed_ref() This is to avoid use-after-free, the @node can be freed in the caller. This error should only be triggered at most once. As if run_one_delayed_ref() failed, we trigger the error message, then causing the call chain to error out: btrfs_run_delayed_refs() `- btrfs_run_delayed_refs() `- btrfs_run_delayed_refs_for_head() `- run_one_delayed_ref() And we will abort the current transaction in btrfs_run_delayed_refs(
CVE-2022-49761
In the Linux kernel, the following vulnerability has been resolved: b ...
GHSA-2x8g-m7hp-f3x8
In the Linux kernel, the following vulnerability has been resolved: btrfs: always report error in run_one_delayed_ref() Currently we have a btrfs_debug() for run_one_delayed_ref() failure, but if end users hit such problem, there will be no chance that btrfs_debug() is enabled. This can lead to very little useful info for debugging. This patch will: - Add extra info for error reporting Including: * logical bytenr * num_bytes * type * action * ref_mod - Replace the btrfs_debug() with btrfs_err() - Move the error reporting into run_one_delayed_ref() This is to avoid use-after-free, the @node can be freed in the caller. This error should only be triggered at most once. As if run_one_delayed_ref() failed, we trigger the error message, then causing the call chain to error out: btrfs_run_delayed_refs() `- btrfs_run_delayed_refs() `- btrfs_run_delayed_refs_for_head() `- run_one_delayed_ref() And we will abort the current transaction in btrfs_run_delayed_re...
BDU:2025-06308
Уязвимость компонента btrfs ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ALT-PU-2023-8448
ALT-PU-2023-8448: package `kernel-image-std-def` update to version 5.10.165-alt1
ALT-PU-2023-8786
ALT-PU-2023-8786: package `kernel-image-std-def` update to version 5.15.90-alt1
ALT-PU-2023-8555
ALT-PU-2023-8555: package `kernel-image-un-def` update to version 5.15.90-alt1
ALT-PU-2023-1124
ALT-PU-2023-1124: package `kernel-image-un-def` update to version 6.1.8-alt1
ROS-20250529-01
Множественные уязвимости kernel-lt
ALT-PU-2023-1282
ALT-PU-2023-1282: package `kernel-image-std-kvm` update to version 5.10.168-alt1
SUSE-SU-2025:01983-1
Security update for the Linux Kernel
ALT-PU-2023-1126
ALT-PU-2023-1126: package `kernel-image-mp` update to version 6.1.8-alt1
ALT-PU-2023-1155
ALT-PU-2023-1155: package `kernel-image-rt` update to version 5.10.165-alt1.rt81
ALT-PU-2023-1154
ALT-PU-2023-1154: package `kernel-image-rt` update to version 5.10.165-alt1.rt81
ALT-PU-2023-7682
ALT-PU-2023-7682: package `kernel-image-rpi-def` update to version 5.15.92-alt2
ALT-PU-2023-7007
ALT-PU-2023-7007: package `kernel-image-rpi-def` update to version 5.15.92-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-2022-49761 In the Linux kernel, the following vulnerability has been resolved: btrfs: always report error in run_one_delayed_ref() Currently we have a btrfs_debug() for run_one_delayed_ref() failure, but if end users hit such problem, there will be no chance that btrfs_debug() is enabled. This can lead to very little useful info for debugging. This patch will: - Add extra info for error reporting Including: * logical bytenr * num_bytes * type * action * ref_mod - Replace the btrfs_debug() with btrfs_err() - Move the error reporting into run_one_delayed_ref() This is to avoid use-after-free, the @node can be freed in the caller. This error should only be triggered at most once. As if run_one_delayed_ref() failed, we trigger the error message, then causing the call chain to error out: btrfs_run_delayed_refs() `- btrfs_run_delayed_refs() `- btrfs_run_delayed_refs_for_head() `- run_one_delayed_ref() And we will abort the current transaction in btrfs_run_delayed_refs(). If we have to run delayed r... | CVSS3: 7.8 | 0% Низкий | больше 1 года назад | |
CVE-2022-49761 In the Linux kernel, the following vulnerability has been resolved: btrfs: always report error in run_one_delayed_ref() Currently we have a btrfs_debug() for run_one_delayed_ref() failure, but if end users hit such problem, there will be no chance that btrfs_debug() is enabled. This can lead to very little useful info for debugging. This patch will: - Add extra info for error reporting Including: * logical bytenr * num_bytes * type * action * ref_mod - Replace the btrfs_debug() with btrfs_err() - Move the error reporting into run_one_delayed_ref() This is to avoid use-after-free, the @node can be freed in the caller. This error should only be triggered at most once. As if run_one_delayed_ref() failed, we trigger the error message, then causing the call chain to error out: btrfs_run_delayed_refs() `- btrfs_run_delayed_refs() `- btrfs_run_delayed_refs_for_head() `- run_one_delayed_ref() And we will abort the current transaction in btrfs_run_delayed_refs(). If we have to run delayed r... | CVSS3: 2.3 | 0% Низкий | больше 1 года назад | |
CVE-2022-49761 In the Linux kernel, the following vulnerability has been resolved: btrfs: always report error in run_one_delayed_ref() Currently we have a btrfs_debug() for run_one_delayed_ref() failure, but if end users hit such problem, there will be no chance that btrfs_debug() is enabled. This can lead to very little useful info for debugging. This patch will: - Add extra info for error reporting Including: * logical bytenr * num_bytes * type * action * ref_mod - Replace the btrfs_debug() with btrfs_err() - Move the error reporting into run_one_delayed_ref() This is to avoid use-after-free, the @node can be freed in the caller. This error should only be triggered at most once. As if run_one_delayed_ref() failed, we trigger the error message, then causing the call chain to error out: btrfs_run_delayed_refs() `- btrfs_run_delayed_refs() `- btrfs_run_delayed_refs_for_head() `- run_one_delayed_ref() And we will abort the current transaction in btrfs_run_delayed_refs( | CVSS3: 7.8 | 0% Низкий | больше 1 года назад | |
CVE-2022-49761 In the Linux kernel, the following vulnerability has been resolved: b ... | CVSS3: 7.8 | 0% Низкий | больше 1 года назад | |
GHSA-2x8g-m7hp-f3x8 In the Linux kernel, the following vulnerability has been resolved: btrfs: always report error in run_one_delayed_ref() Currently we have a btrfs_debug() for run_one_delayed_ref() failure, but if end users hit such problem, there will be no chance that btrfs_debug() is enabled. This can lead to very little useful info for debugging. This patch will: - Add extra info for error reporting Including: * logical bytenr * num_bytes * type * action * ref_mod - Replace the btrfs_debug() with btrfs_err() - Move the error reporting into run_one_delayed_ref() This is to avoid use-after-free, the @node can be freed in the caller. This error should only be triggered at most once. As if run_one_delayed_ref() failed, we trigger the error message, then causing the call chain to error out: btrfs_run_delayed_refs() `- btrfs_run_delayed_refs() `- btrfs_run_delayed_refs_for_head() `- run_one_delayed_ref() And we will abort the current transaction in btrfs_run_delayed_re... | CVSS3: 7.8 | 0% Низкий | больше 1 года назад | |
BDU:2025-06308 Уязвимость компонента btrfs ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 7.8 | 0% Низкий | больше 1 года назад | |
ALT-PU-2023-8448 ALT-PU-2023-8448: package `kernel-image-std-def` update to version 5.10.165-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
ALT-PU-2023-8786 ALT-PU-2023-8786: package `kernel-image-std-def` update to version 5.15.90-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
ALT-PU-2023-8555 ALT-PU-2023-8555: package `kernel-image-un-def` update to version 5.15.90-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
ALT-PU-2023-1124 ALT-PU-2023-1124: package `kernel-image-un-def` update to version 6.1.8-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
ROS-20250529-01 Множественные уязвимости kernel-lt | CVSS3: 7.8 | больше 1 года назад | ||
ALT-PU-2023-1282 ALT-PU-2023-1282: package `kernel-image-std-kvm` update to version 5.10.168-alt1 | CVSS3: 8.8 | больше 3 лет назад | ||
SUSE-SU-2025:01983-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2023-1126 ALT-PU-2023-1126: package `kernel-image-mp` update to version 6.1.8-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
ALT-PU-2023-1155 ALT-PU-2023-1155: package `kernel-image-rt` update to version 5.10.165-alt1.rt81 | CVSS3: 8.4 | почти 4 года назад | ||
ALT-PU-2023-1154 ALT-PU-2023-1154: package `kernel-image-rt` update to version 5.10.165-alt1.rt81 | CVSS3: 8.4 | почти 4 года назад | ||
ALT-PU-2023-7682 ALT-PU-2023-7682: package `kernel-image-rpi-def` update to version 5.15.92-alt2 | CVSS3: 9.3 | почти 3 года назад | ||
ALT-PU-2023-7007 ALT-PU-2023-7007: package `kernel-image-rpi-def` update to version 5.15.92-alt1 | CVSS3: 9.3 | около 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 лет назад |
Уязвимостей на страницу