Количество 28
Количество 28

CVE-2025-22115
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix block group refcount race in btrfs_create_pending_block_groups() Block group creation is done in two phases, which results in a slightly unintuitive property: a block group can be allocated/deallocated from after btrfs_make_block_group() adds it to the space_info with btrfs_add_bg_to_space_info(), but before creation is completely completed in btrfs_create_pending_block_groups(). As a result, it is possible for a block group to go unused and have 'btrfs_mark_bg_unused' called on it concurrently with 'btrfs_create_pending_block_groups'. This causes a number of issues, which were fixed with the block group flag 'BLOCK_GROUP_FLAG_NEW'. However, this fix is not quite complete. Since it does not use the unused_bg_lock, it is possible for the following race to occur: btrfs_create_pending_block_groups btrfs_mark_bg_unused if list_empty // false list_del_init clear_bit else if (test_bit) // true list_m...

CVE-2025-22115
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix block group refcount race in btrfs_create_pending_block_groups() Block group creation is done in two phases, which results in a slightly unintuitive property: a block group can be allocated/deallocated from after btrfs_make_block_group() adds it to the space_info with btrfs_add_bg_to_space_info(), but before creation is completely completed in btrfs_create_pending_block_groups(). As a result, it is possible for a block group to go unused and have 'btrfs_mark_bg_unused' called on it concurrently with 'btrfs_create_pending_block_groups'. This causes a number of issues, which were fixed with the block group flag 'BLOCK_GROUP_FLAG_NEW'. However, this fix is not quite complete. Since it does not use the unused_bg_lock, it is possible for the following race to occur: btrfs_create_pending_block_groups btrfs_mark_bg_unused if list_empty // false list_del_init clear_bit else if (test_bit) // true list_m...

CVE-2025-22115
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix block group refcount race in btrfs_create_pending_block_groups() Block group creation is done in two phases, which results in a slightly unintuitive property: a block group can be allocated/deallocated from after btrfs_make_block_group() adds it to the space_info with btrfs_add_bg_to_space_info(), but before creation is completely completed in btrfs_create_pending_block_groups(). As a result, it is possible for a block group to go unused and have 'btrfs_mark_bg_unused' called on it concurrently with 'btrfs_create_pending_block_groups'. This causes a number of issues, which were fixed with the block group flag 'BLOCK_GROUP_FLAG_NEW'. However, this fix is not quite complete. Since it does not use the unused_bg_lock, it is possible for the following race to occur: btrfs_create_pending_block_groups btrfs_mark_bg_unused if list_empty // false list_
CVE-2025-22115
In the Linux kernel, the following vulnerability has been resolved: b ...

SUSE-SU-2025:02514-1
Security update for the Linux Kernel (Live Patch 10 for SLE 15 SP6)

SUSE-SU-2025:02439-1
Security update for the Linux Kernel RT (Live Patch 10 for SLE 15 SP6)
GHSA-h52v-87c4-f7qg
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix block group refcount race in btrfs_create_pending_block_groups() Block group creation is done in two phases, which results in a slightly unintuitive property: a block group can be allocated/deallocated from after btrfs_make_block_group() adds it to the space_info with btrfs_add_bg_to_space_info(), but before creation is completely completed in btrfs_create_pending_block_groups(). As a result, it is possible for a block group to go unused and have 'btrfs_mark_bg_unused' called on it concurrently with 'btrfs_create_pending_block_groups'. This causes a number of issues, which were fixed with the block group flag 'BLOCK_GROUP_FLAG_NEW'. However, this fix is not quite complete. Since it does not use the unused_bg_lock, it is possible for the following race to occur: btrfs_create_pending_block_groups btrfs_mark_bg_unused if list_empty // false li...

SUSE-SU-2025:02442-1
Security update for the Linux Kernel (Live Patch 9 for SLE 15 SP6)

SUSE-SU-2025:02405-1
Security update for the Linux Kernel RT (Live Patch 9 for SLE 15 SP6)

SUSE-SU-2025:02385-1
Security update for the Linux Kernel RT (Live Patch 8 for SLE 15 SP6)

SUSE-SU-2025:02421-1
Security update for the Linux Kernel (Live Patch 7 for SLE 15 SP6)

SUSE-SU-2025:02413-1
Security update for the Linux Kernel RT (Live Patch 7 for SLE 15 SP6)

SUSE-SU-2025:02433-1
Security update for the Linux Kernel (Live Patch 6 for SLE 15 SP6)

SUSE-SU-2025:02387-1
Security update for the Linux Kernel RT (Live Patch 6 for SLE 15 SP6)

SUSE-SU-2025:02412-1
Security update for the Linux Kernel RT (Live Patch 5 for SLE 15 SP6)

SUSE-SU-2025:02449-1
Security update for the Linux Kernel (Live Patch 4 for SLE 15 SP6)

SUSE-SU-2025:02420-1
Security update for the Linux Kernel RT (Live Patch 2 for SLE 15 SP6)

SUSE-SU-2025:02411-1
Security update for the Linux Kernel RT (Live Patch 4 for SLE 15 SP6)

SUSE-SU-2025:02389-1
Security update for the Linux Kernel RT (Live Patch 3 for SLE 15 SP6)

SUSE-SU-2025:02388-1
Security update for the Linux Kernel RT (Live Patch 1 for SLE 15 SP6)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
---|---|---|---|---|
![]() | CVE-2025-22115 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix block group refcount race in btrfs_create_pending_block_groups() Block group creation is done in two phases, which results in a slightly unintuitive property: a block group can be allocated/deallocated from after btrfs_make_block_group() adds it to the space_info with btrfs_add_bg_to_space_info(), but before creation is completely completed in btrfs_create_pending_block_groups(). As a result, it is possible for a block group to go unused and have 'btrfs_mark_bg_unused' called on it concurrently with 'btrfs_create_pending_block_groups'. This causes a number of issues, which were fixed with the block group flag 'BLOCK_GROUP_FLAG_NEW'. However, this fix is not quite complete. Since it does not use the unused_bg_lock, it is possible for the following race to occur: btrfs_create_pending_block_groups btrfs_mark_bg_unused if list_empty // false list_del_init clear_bit else if (test_bit) // true list_m... | 0% Низкий | 5 месяцев назад | |
![]() | CVE-2025-22115 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix block group refcount race in btrfs_create_pending_block_groups() Block group creation is done in two phases, which results in a slightly unintuitive property: a block group can be allocated/deallocated from after btrfs_make_block_group() adds it to the space_info with btrfs_add_bg_to_space_info(), but before creation is completely completed in btrfs_create_pending_block_groups(). As a result, it is possible for a block group to go unused and have 'btrfs_mark_bg_unused' called on it concurrently with 'btrfs_create_pending_block_groups'. This causes a number of issues, which were fixed with the block group flag 'BLOCK_GROUP_FLAG_NEW'. However, this fix is not quite complete. Since it does not use the unused_bg_lock, it is possible for the following race to occur: btrfs_create_pending_block_groups btrfs_mark_bg_unused if list_empty // false list_del_init clear_bit else if (test_bit) // true list_m... | CVSS3: 5.5 | 0% Низкий | 5 месяцев назад |
![]() | CVE-2025-22115 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix block group refcount race in btrfs_create_pending_block_groups() Block group creation is done in two phases, which results in a slightly unintuitive property: a block group can be allocated/deallocated from after btrfs_make_block_group() adds it to the space_info with btrfs_add_bg_to_space_info(), but before creation is completely completed in btrfs_create_pending_block_groups(). As a result, it is possible for a block group to go unused and have 'btrfs_mark_bg_unused' called on it concurrently with 'btrfs_create_pending_block_groups'. This causes a number of issues, which were fixed with the block group flag 'BLOCK_GROUP_FLAG_NEW'. However, this fix is not quite complete. Since it does not use the unused_bg_lock, it is possible for the following race to occur: btrfs_create_pending_block_groups btrfs_mark_bg_unused if list_empty // false list_ | 0% Низкий | 5 месяцев назад | |
CVE-2025-22115 In the Linux kernel, the following vulnerability has been resolved: b ... | 0% Низкий | 5 месяцев назад | ||
![]() | SUSE-SU-2025:02514-1 Security update for the Linux Kernel (Live Patch 10 for SLE 15 SP6) | 0% Низкий | около 2 месяцев назад | |
![]() | SUSE-SU-2025:02439-1 Security update for the Linux Kernel RT (Live Patch 10 for SLE 15 SP6) | 0% Низкий | около 2 месяцев назад | |
GHSA-h52v-87c4-f7qg In the Linux kernel, the following vulnerability has been resolved: btrfs: fix block group refcount race in btrfs_create_pending_block_groups() Block group creation is done in two phases, which results in a slightly unintuitive property: a block group can be allocated/deallocated from after btrfs_make_block_group() adds it to the space_info with btrfs_add_bg_to_space_info(), but before creation is completely completed in btrfs_create_pending_block_groups(). As a result, it is possible for a block group to go unused and have 'btrfs_mark_bg_unused' called on it concurrently with 'btrfs_create_pending_block_groups'. This causes a number of issues, which were fixed with the block group flag 'BLOCK_GROUP_FLAG_NEW'. However, this fix is not quite complete. Since it does not use the unused_bg_lock, it is possible for the following race to occur: btrfs_create_pending_block_groups btrfs_mark_bg_unused if list_empty // false li... | 0% Низкий | 5 месяцев назад | ||
![]() | SUSE-SU-2025:02442-1 Security update for the Linux Kernel (Live Patch 9 for SLE 15 SP6) | около 2 месяцев назад | ||
![]() | SUSE-SU-2025:02405-1 Security update for the Linux Kernel RT (Live Patch 9 for SLE 15 SP6) | около 2 месяцев назад | ||
![]() | SUSE-SU-2025:02385-1 Security update for the Linux Kernel RT (Live Patch 8 for SLE 15 SP6) | около 2 месяцев назад | ||
![]() | SUSE-SU-2025:02421-1 Security update for the Linux Kernel (Live Patch 7 for SLE 15 SP6) | около 2 месяцев назад | ||
![]() | SUSE-SU-2025:02413-1 Security update for the Linux Kernel RT (Live Patch 7 for SLE 15 SP6) | около 2 месяцев назад | ||
![]() | SUSE-SU-2025:02433-1 Security update for the Linux Kernel (Live Patch 6 for SLE 15 SP6) | около 2 месяцев назад | ||
![]() | SUSE-SU-2025:02387-1 Security update for the Linux Kernel RT (Live Patch 6 for SLE 15 SP6) | около 2 месяцев назад | ||
![]() | SUSE-SU-2025:02412-1 Security update for the Linux Kernel RT (Live Patch 5 for SLE 15 SP6) | около 2 месяцев назад | ||
![]() | SUSE-SU-2025:02449-1 Security update for the Linux Kernel (Live Patch 4 for SLE 15 SP6) | около 2 месяцев назад | ||
![]() | SUSE-SU-2025:02420-1 Security update for the Linux Kernel RT (Live Patch 2 for SLE 15 SP6) | около 2 месяцев назад | ||
![]() | SUSE-SU-2025:02411-1 Security update for the Linux Kernel RT (Live Patch 4 for SLE 15 SP6) | около 2 месяцев назад | ||
![]() | SUSE-SU-2025:02389-1 Security update for the Linux Kernel RT (Live Patch 3 for SLE 15 SP6) | около 2 месяцев назад | ||
![]() | SUSE-SU-2025:02388-1 Security update for the Linux Kernel RT (Live Patch 1 for SLE 15 SP6) | около 2 месяцев назад |
Уязвимостей на страницу