Поиск уязвимостей
Количество 22
Количество 22
CVE-2025-68358
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document regarding memory barrier ordering guarantees: (*) These guarantees do not apply to bitfields, because compilers often generate code to modify these using non-atomic read-modify-write sequences. Do not attempt to use bitfields to synchronize parallel algorithms. (*) Even in cases where bitfields are protected by locks, all fields in a given bitfield must be protected by one lock. If two fields in a given bitfield are protected by different locks, the compiler's non-atomic read-modify-write sequences can cause an update to one field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info { struct btrfs_fs_info * fs_info; /* 0 8 */ struct btrfs_space_info * parent; ...
CVE-2025-68358
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document regarding memory barrier ordering guarantees: (*) These guarantees do not apply to bitfields, because compilers often generate code to modify these using non-atomic read-modify-write sequences. Do not attempt to use bitfields to synchronize parallel algorithms. (*) Even in cases where bitfields are protected by locks, all fields in a given bitfield must be protected by one lock. If two fields in a given bitfield are protected by different locks, the compiler's non-atomic read-modify-write sequences can cause an update to one field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info { struct btrfs_fs_info * fs_info; /* 0 8 */ struct btrfs_space_info * parent; ...
CVE-2025-68358
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document regarding memory barrier ordering guarantees: (*) These guarantees do not apply to bitfields, because compilers often generate code to modify these using non-atomic read-modify-write sequences. Do not attempt to use bitfields to synchronize parallel algorithms. (*) Even in cases where bitfields are protected by locks, all fields in a given bitfield must be protected by one lock. If two fields in a given bitfield are protected by different locks, the compiler's non-atomic read-modify-write sequences can cause an update to one field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info { struct btrfs_fs_info * fs_info; /* 0
CVE-2025-68358
btrfs: fix racy bitfield write in btrfs_clear_space_info_full()
CVE-2025-68358
In the Linux kernel, the following vulnerability has been resolved: b ...
GHSA-2m44-r2x5-4q79
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document regarding memory barrier ordering guarantees: (*) These guarantees do not apply to bitfields, because compilers often generate code to modify these using non-atomic read-modify-write sequences. Do not attempt to use bitfields to synchronize parallel algorithms. (*) Even in cases where bitfields are protected by locks, all fields in a given bitfield must be protected by one lock. If two fields in a given bitfield are protected by different locks, the compiler's non-atomic read-modify-write sequences can cause an update to one field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info { struct btrfs_fs_info * fs_info; /* ...
BDU:2026-11427
Уязвимость функции btrfs_clear_space_info_full() модуля btrfs ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260929-80-0133
Уязвимость kernel-lt
ROS-20260929-73-0115
Уязвимость kernel-lt
SUSE-SU-2026:4892-1
Security update for the Linux Kernel
SUSE-SU-2026:4940-1
Security update for the Linux Kernel
SUSE-SU-2026:4935-1
Security update for the Linux Kernel
ELSA-2026-50232
ELSA-2026-50232: Unbreakable Enterprise kernel security update (IMPORTANT)
ELSA-2026-50160
ELSA-2026-50160: Unbreakable Enterprise kernel security update (IMPORTANT)
ALT-PU-2026-3601
ALT-PU-2026-3601: package `kernel-image-6.12` update to version 6.12.68-alt1
ALT-PU-2026-3600
ALT-PU-2026-3600: package `kernel-image-rt` update to version 6.12.68-alt1
ALT-PU-2026-1774
ALT-PU-2026-1774: package `kernel-image-pine` update to version 6.18.7-alt1
ALT-PU-2026-4126
ALT-PU-2026-4126: package `kernel-image-un-def` update to version 6.1.166-alt1
ELSA-2026-50372
ELSA-2026-50372: Unbreakable Enterprise kernel security update (IMPORTANT)
openSUSE-SU-2026:21910-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2025-68358 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document regarding memory barrier ordering guarantees: (*) These guarantees do not apply to bitfields, because compilers often generate code to modify these using non-atomic read-modify-write sequences. Do not attempt to use bitfields to synchronize parallel algorithms. (*) Even in cases where bitfields are protected by locks, all fields in a given bitfield must be protected by one lock. If two fields in a given bitfield are protected by different locks, the compiler's non-atomic read-modify-write sequences can cause an update to one field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info { struct btrfs_fs_info * fs_info; /* 0 8 */ struct btrfs_space_info * parent; ... | CVSS3: 5.5 | 0% Низкий | 11 месяцев назад | |
CVE-2025-68358 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document regarding memory barrier ordering guarantees: (*) These guarantees do not apply to bitfields, because compilers often generate code to modify these using non-atomic read-modify-write sequences. Do not attempt to use bitfields to synchronize parallel algorithms. (*) Even in cases where bitfields are protected by locks, all fields in a given bitfield must be protected by one lock. If two fields in a given bitfield are protected by different locks, the compiler's non-atomic read-modify-write sequences can cause an update to one field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info { struct btrfs_fs_info * fs_info; /* 0 8 */ struct btrfs_space_info * parent; ... | 0% Низкий | 11 месяцев назад | ||
CVE-2025-68358 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document regarding memory barrier ordering guarantees: (*) These guarantees do not apply to bitfields, because compilers often generate code to modify these using non-atomic read-modify-write sequences. Do not attempt to use bitfields to synchronize parallel algorithms. (*) Even in cases where bitfields are protected by locks, all fields in a given bitfield must be protected by one lock. If two fields in a given bitfield are protected by different locks, the compiler's non-atomic read-modify-write sequences can cause an update to one field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info { struct btrfs_fs_info * fs_info; /* 0 | CVSS3: 5.5 | 0% Низкий | 11 месяцев назад | |
CVE-2025-68358 btrfs: fix racy bitfield write in btrfs_clear_space_info_full() | CVSS3: 5.5 | 0% Низкий | 11 месяцев назад | |
CVE-2025-68358 In the Linux kernel, the following vulnerability has been resolved: b ... | CVSS3: 5.5 | 0% Низкий | 11 месяцев назад | |
GHSA-2m44-r2x5-4q79 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document regarding memory barrier ordering guarantees: (*) These guarantees do not apply to bitfields, because compilers often generate code to modify these using non-atomic read-modify-write sequences. Do not attempt to use bitfields to synchronize parallel algorithms. (*) Even in cases where bitfields are protected by locks, all fields in a given bitfield must be protected by one lock. If two fields in a given bitfield are protected by different locks, the compiler's non-atomic read-modify-write sequences can cause an update to one field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info { struct btrfs_fs_info * fs_info; /* ... | CVSS3: 5.5 | 0% Низкий | 11 месяцев назад | |
BDU:2026-11427 Уязвимость функции btrfs_clear_space_info_full() модуля btrfs ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
ROS-20260929-80-0133 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад | |
ROS-20260929-73-0115 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад | |
SUSE-SU-2026:4892-1 Security update for the Linux Kernel | 16 дней назад | |||
SUSE-SU-2026:4940-1 Security update for the Linux Kernel | 10 дней назад | |||
SUSE-SU-2026:4935-1 Security update for the Linux Kernel | 10 дней назад | |||
ELSA-2026-50232 ELSA-2026-50232: Unbreakable Enterprise kernel security update (IMPORTANT) | 7 месяцев назад | |||
ELSA-2026-50160 ELSA-2026-50160: Unbreakable Enterprise kernel security update (IMPORTANT) | 8 месяцев назад | |||
ALT-PU-2026-3601 ALT-PU-2026-3601: package `kernel-image-6.12` update to version 6.12.68-alt1 | CVSS3: 8.8 | 9 месяцев назад | ||
ALT-PU-2026-3600 ALT-PU-2026-3600: package `kernel-image-rt` update to version 6.12.68-alt1 | CVSS3: 8.8 | 9 месяцев назад | ||
ALT-PU-2026-1774 ALT-PU-2026-1774: package `kernel-image-pine` update to version 6.18.7-alt1 | CVSS3: 8.8 | 10 месяцев назад | ||
ALT-PU-2026-4126 ALT-PU-2026-4126: package `kernel-image-un-def` update to version 6.1.166-alt1 | CVSS3: 9.8 | 8 месяцев назад | ||
ELSA-2026-50372 ELSA-2026-50372: Unbreakable Enterprise kernel security update (IMPORTANT) | 4 месяца назад | |||
openSUSE-SU-2026:21910-1 Security update for the Linux Kernel | около 2 месяцев назад |
Уязвимостей на страницу