Поиск уязвимостей
Количество 22
Количество 22
CVE-2023-53618
In the Linux kernel, the following vulnerability has been resolved: btrfs: reject invalid reloc tree root keys with stack dump [BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge(). That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree. [CAUSE] After more debugging output, it turns out we had an invalid reloc tree: BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17 Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it's a reloc tree for quota tree. But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won't be shared with other trees. Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag). Thus this new debug output proves my previous assumption that corrup...
CVE-2023-53618
In the Linux kernel, the following vulnerability has been resolved: btrfs: reject invalid reloc tree root keys with stack dump [BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge(). That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree. [CAUSE] After more debugging output, it turns out we had an invalid reloc tree: BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17 Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it's a reloc tree for quota tree. But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won't be shared with other trees. Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag). Thus this new debug output proves my previous assumption that corrup...
CVE-2023-53618
In the Linux kernel, the following vulnerability has been resolved: btrfs: reject invalid reloc tree root keys with stack dump [BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge(). That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree. [CAUSE] After more debugging output, it turns out we had an invalid reloc tree: BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17 Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it's a reloc tree for quota tree. But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won't be shared with other trees. Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag). Thus this new debug output proves my previous assumption tha
CVE-2023-53618
In the Linux kernel, the following vulnerability has been resolved: b ...
ROS-20260826-73-0020
Уязвимость kernel-lt
GHSA-2244-8r8j-955v
In the Linux kernel, the following vulnerability has been resolved: btrfs: reject invalid reloc tree root keys with stack dump [BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge(). That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree. [CAUSE] After more debugging output, it turns out we had an invalid reloc tree: BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17 Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it's a reloc tree for quota tree. But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won't be shared with other trees. Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag). Thus this new debug output proves my previous assumption ...
BDU:2026-15238
Уязвимость ядра операционной системы Linux, связанная с реализацией некорректного потока управления, позволяющая нарушителю вызвать отказ в обслуживании
ALT-PU-2019-2842
ALT-PU-2019-2842: package `kernel-image-un-def` update to version 5.3.0-alt1
ALT-PU-2023-8813
ALT-PU-2023-8813: package `kernel-image-std-def` update to version 6.1.46-alt1
ALT-PU-2023-8884
ALT-PU-2023-8884: package `kernel-image-un-def` update to version 6.4.11-alt1
ALT-PU-2023-8569
ALT-PU-2023-8569: package `kernel-image-un-def` update to version 6.1.49-alt1
ALT-PU-2023-5182
ALT-PU-2023-5182: package `kernel-image-mp` update to version 6.4.12-alt1
ALT-PU-2023-5818
ALT-PU-2023-5818: package `kernel-image-pine` update to version 6.4.16-alt1
SUSE-SU-2025:4128-1
Security update for the Linux Kernel
SUSE-SU-2025:4301-1
Security update for the Linux Kernel
SUSE-SU-2025:4140-1
Security update for the Linux Kernel
ALT-PU-2023-8725
ALT-PU-2023-8725: package `kernel-image-rt` update to version 6.1.46-alt1.rt13
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
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2023-53618 In the Linux kernel, the following vulnerability has been resolved: btrfs: reject invalid reloc tree root keys with stack dump [BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge(). That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree. [CAUSE] After more debugging output, it turns out we had an invalid reloc tree: BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17 Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it's a reloc tree for quota tree. But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won't be shared with other trees. Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag). Thus this new debug output proves my previous assumption that corrup... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2023-53618 In the Linux kernel, the following vulnerability has been resolved: btrfs: reject invalid reloc tree root keys with stack dump [BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge(). That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree. [CAUSE] After more debugging output, it turns out we had an invalid reloc tree: BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17 Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it's a reloc tree for quota tree. But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won't be shared with other trees. Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag). Thus this new debug output proves my previous assumption that corrup... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2023-53618 In the Linux kernel, the following vulnerability has been resolved: btrfs: reject invalid reloc tree root keys with stack dump [BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge(). That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree. [CAUSE] After more debugging output, it turns out we had an invalid reloc tree: BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17 Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it's a reloc tree for quota tree. But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won't be shared with other trees. Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag). Thus this new debug output proves my previous assumption tha | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2023-53618 In the Linux kernel, the following vulnerability has been resolved: b ... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
ROS-20260826-73-0020 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 3 месяца назад | |
GHSA-2244-8r8j-955v In the Linux kernel, the following vulnerability has been resolved: btrfs: reject invalid reloc tree root keys with stack dump [BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge(). That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree. [CAUSE] After more debugging output, it turns out we had an invalid reloc tree: BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17 Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it's a reloc tree for quota tree. But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won't be shared with other trees. Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag). Thus this new debug output proves my previous assumption ... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
BDU:2026-15238 Уязвимость ядра операционной системы Linux, связанная с реализацией некорректного потока управления, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
ALT-PU-2019-2842 ALT-PU-2019-2842: package `kernel-image-un-def` update to version 5.3.0-alt1 | CVSS3: 7.8 | около 7 лет назад | ||
ALT-PU-2023-8813 ALT-PU-2023-8813: package `kernel-image-std-def` update to version 6.1.46-alt1 | CVSS3: 7.8 | больше 3 лет назад | ||
ALT-PU-2023-8884 ALT-PU-2023-8884: package `kernel-image-un-def` update to version 6.4.11-alt1 | CVSS3: 7.8 | больше 3 лет назад | ||
ALT-PU-2023-8569 ALT-PU-2023-8569: package `kernel-image-un-def` update to version 6.1.49-alt1 | CVSS3: 7.8 | около 3 лет назад | ||
ALT-PU-2023-5182 ALT-PU-2023-5182: package `kernel-image-mp` update to version 6.4.12-alt1 | CVSS3: 7.8 | около 3 лет назад | ||
ALT-PU-2023-5818 ALT-PU-2023-5818: package `kernel-image-pine` update to version 6.4.16-alt1 | CVSS3: 10 | около 3 лет назад | ||
SUSE-SU-2025:4128-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:4301-1 Security update for the Linux Kernel | 12 месяцев назад | |||
SUSE-SU-2025:4140-1 Security update for the Linux Kernel | около 1 года назад | |||
ALT-PU-2023-8725 ALT-PU-2023-8725: package `kernel-image-rt` update to version 6.1.46-alt1.rt13 | CVSS3: 8.8 | больше 3 лет назад | ||
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 года назад |
Уязвимостей на страницу