Поиск уязвимостей
Количество 21
Количество 21
CVE-2024-26727
In the Linux kernel, the following vulnerability has been resolved: btrfs: do not ASSERT() if the newly created subvolume already got read [BUG] There is a syzbot crash, triggered by the ASSERT() during subvolume creation: assertion failed: !anon_dev, in fs/btrfs/disk-io.c:1319 ------------[ cut here ]------------ kernel BUG at fs/btrfs/disk-io.c:1319! invalid opcode: 0000 [#1] PREEMPT SMP KASAN RIP: 0010:btrfs_get_root_ref.part.0+0x9aa/0xa60 <TASK> btrfs_get_new_fs_root+0xd3/0xf0 create_subvol+0xd02/0x1650 btrfs_mksubvol+0xe95/0x12b0 __btrfs_ioctl_snap_create+0x2f9/0x4f0 btrfs_ioctl_snap_create+0x16b/0x200 btrfs_ioctl+0x35f0/0x5cf0 __x64_sys_ioctl+0x19d/0x210 do_syscall_64+0x3f/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b ---[ end trace 0000000000000000 ]--- [CAUSE] During create_subvol(), after inserting root item for the newly created subvolume, we would trigger btrfs_get_new_fs_root() to get the btrfs_root of that subvolume. The idea here is, we have preallocated an anonymous d...
CVE-2024-26727
In the Linux kernel, the following vulnerability has been resolved: btrfs: do not ASSERT() if the newly created subvolume already got read [BUG] There is a syzbot crash, triggered by the ASSERT() during subvolume creation: assertion failed: !anon_dev, in fs/btrfs/disk-io.c:1319 ------------[ cut here ]------------ kernel BUG at fs/btrfs/disk-io.c:1319! invalid opcode: 0000 [#1] PREEMPT SMP KASAN RIP: 0010:btrfs_get_root_ref.part.0+0x9aa/0xa60 <TASK> btrfs_get_new_fs_root+0xd3/0xf0 create_subvol+0xd02/0x1650 btrfs_mksubvol+0xe95/0x12b0 __btrfs_ioctl_snap_create+0x2f9/0x4f0 btrfs_ioctl_snap_create+0x16b/0x200 btrfs_ioctl+0x35f0/0x5cf0 __x64_sys_ioctl+0x19d/0x210 do_syscall_64+0x3f/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b ---[ end trace 0000000000000000 ]--- [CAUSE] During create_subvol(), after inserting root item for the newly created subvolume, we would trigger btrfs_get_new_fs_root() to get the btrfs_root of that subvolume. The idea here is, we have preallocated an anonymous d...
CVE-2024-26727
In the Linux kernel, the following vulnerability has been resolved: btrfs: do not ASSERT() if the newly created subvolume already got read [BUG] There is a syzbot crash, triggered by the ASSERT() during subvolume creation: assertion failed: !anon_dev, in fs/btrfs/disk-io.c:1319 ------------[ cut here ]------------ kernel BUG at fs/btrfs/disk-io.c:1319! invalid opcode: 0000 [#1] PREEMPT SMP KASAN RIP: 0010:btrfs_get_root_ref.part.0+0x9aa/0xa60 <TASK> btrfs_get_new_fs_root+0xd3/0xf0 create_subvol+0xd02/0x1650 btrfs_mksubvol+0xe95/0x12b0 __btrfs_ioctl_snap_create+0x2f9/0x4f0 btrfs_ioctl_snap_create+0x16b/0x200 btrfs_ioctl+0x35f0/0x5cf0 __x64_sys_ioctl+0x19d/0x210 do_syscall_64+0x3f/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b ---[ end trace 0000000000000000 ]--- [CAUSE] During create_subvol(), after inserting root item for the newly created subvolume, we would trigger btrfs_get_new_fs_root() to get the btrfs_root of that subvolume. The idea here is, we have
CVE-2024-26727
In the Linux kernel, the following vulnerability has been resolved: b ...
GHSA-w9mj-34hr-82rj
In the Linux kernel, the following vulnerability has been resolved: btrfs: do not ASSERT() if the newly created subvolume already got read [BUG] There is a syzbot crash, triggered by the ASSERT() during subvolume creation: assertion failed: !anon_dev, in fs/btrfs/disk-io.c:1319 ------------[ cut here ]------------ kernel BUG at fs/btrfs/disk-io.c:1319! invalid opcode: 0000 [#1] PREEMPT SMP KASAN RIP: 0010:btrfs_get_root_ref.part.0+0x9aa/0xa60 <TASK> btrfs_get_new_fs_root+0xd3/0xf0 create_subvol+0xd02/0x1650 btrfs_mksubvol+0xe95/0x12b0 __btrfs_ioctl_snap_create+0x2f9/0x4f0 btrfs_ioctl_snap_create+0x16b/0x200 btrfs_ioctl+0x35f0/0x5cf0 __x64_sys_ioctl+0x19d/0x210 do_syscall_64+0x3f/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b ---[ end trace 0000000000000000 ]--- [CAUSE] During create_subvol(), after inserting root item for the newly created subvolume, we would trigger btrfs_get_new_fs_root() to get the btrfs_root of that subvolume. The idea here is, we h...
BDU:2024-08676
Уязвимость компонента btrfs ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20241021-09
Множественные уязвимости kernel-lt
SUSE-SU-2024:1641-1
Security update for the Linux Kernel
ALT-PU-2024-2868
ALT-PU-2024-2868: package `kernel-image-un-def` update to version 6.1.79-alt1
ALT-PU-2024-18361
ALT-PU-2024-18361: package `kernel-image-std-def` update to version 6.1.79-alt1
ALT-PU-2024-3144
ALT-PU-2024-3144: package `kernel-image-rt` update to version 6.1.79-alt1.rt25
ALT-PU-2024-18464
ALT-PU-2024-18464: package `kernel-image-un-def` update to version 6.6.18-alt1
ALT-PU-2024-18207
ALT-PU-2024-18207: package `kernel-image-pine` update to version 6.6.18-alt1
ALT-PU-2024-3273
ALT-PU-2024-3273: package `kernel-image-rt` update to version 5.10.210-alt1.rt102
SUSE-SU-2024:1490-1
Security update for the Linux Kernel
ALT-PU-2024-3457
ALT-PU-2024-3457: package `kernel-image-std-def` update to version 5.10.211-alt1
SUSE-SU-2024:1659-1
Security update for the Linux Kernel
SUSE-SU-2024:1663-1
Security update for the Linux Kernel
ALT-PU-2024-3415
ALT-PU-2024-3415: package `kernel-image-mp` update to version 6.7.8-alt1
ALT-PU-2024-6818
ALT-PU-2024-6818: package `kernel-image-rpi-un` update to version 6.6.23-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-26727 In the Linux kernel, the following vulnerability has been resolved: btrfs: do not ASSERT() if the newly created subvolume already got read [BUG] There is a syzbot crash, triggered by the ASSERT() during subvolume creation: assertion failed: !anon_dev, in fs/btrfs/disk-io.c:1319 ------------[ cut here ]------------ kernel BUG at fs/btrfs/disk-io.c:1319! invalid opcode: 0000 [#1] PREEMPT SMP KASAN RIP: 0010:btrfs_get_root_ref.part.0+0x9aa/0xa60 <TASK> btrfs_get_new_fs_root+0xd3/0xf0 create_subvol+0xd02/0x1650 btrfs_mksubvol+0xe95/0x12b0 __btrfs_ioctl_snap_create+0x2f9/0x4f0 btrfs_ioctl_snap_create+0x16b/0x200 btrfs_ioctl+0x35f0/0x5cf0 __x64_sys_ioctl+0x19d/0x210 do_syscall_64+0x3f/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b ---[ end trace 0000000000000000 ]--- [CAUSE] During create_subvol(), after inserting root item for the newly created subvolume, we would trigger btrfs_get_new_fs_root() to get the btrfs_root of that subvolume. The idea here is, we have preallocated an anonymous d... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26727 In the Linux kernel, the following vulnerability has been resolved: btrfs: do not ASSERT() if the newly created subvolume already got read [BUG] There is a syzbot crash, triggered by the ASSERT() during subvolume creation: assertion failed: !anon_dev, in fs/btrfs/disk-io.c:1319 ------------[ cut here ]------------ kernel BUG at fs/btrfs/disk-io.c:1319! invalid opcode: 0000 [#1] PREEMPT SMP KASAN RIP: 0010:btrfs_get_root_ref.part.0+0x9aa/0xa60 <TASK> btrfs_get_new_fs_root+0xd3/0xf0 create_subvol+0xd02/0x1650 btrfs_mksubvol+0xe95/0x12b0 __btrfs_ioctl_snap_create+0x2f9/0x4f0 btrfs_ioctl_snap_create+0x16b/0x200 btrfs_ioctl+0x35f0/0x5cf0 __x64_sys_ioctl+0x19d/0x210 do_syscall_64+0x3f/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b ---[ end trace 0000000000000000 ]--- [CAUSE] During create_subvol(), after inserting root item for the newly created subvolume, we would trigger btrfs_get_new_fs_root() to get the btrfs_root of that subvolume. The idea here is, we have preallocated an anonymous d... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26727 In the Linux kernel, the following vulnerability has been resolved: btrfs: do not ASSERT() if the newly created subvolume already got read [BUG] There is a syzbot crash, triggered by the ASSERT() during subvolume creation: assertion failed: !anon_dev, in fs/btrfs/disk-io.c:1319 ------------[ cut here ]------------ kernel BUG at fs/btrfs/disk-io.c:1319! invalid opcode: 0000 [#1] PREEMPT SMP KASAN RIP: 0010:btrfs_get_root_ref.part.0+0x9aa/0xa60 <TASK> btrfs_get_new_fs_root+0xd3/0xf0 create_subvol+0xd02/0x1650 btrfs_mksubvol+0xe95/0x12b0 __btrfs_ioctl_snap_create+0x2f9/0x4f0 btrfs_ioctl_snap_create+0x16b/0x200 btrfs_ioctl+0x35f0/0x5cf0 __x64_sys_ioctl+0x19d/0x210 do_syscall_64+0x3f/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b ---[ end trace 0000000000000000 ]--- [CAUSE] During create_subvol(), after inserting root item for the newly created subvolume, we would trigger btrfs_get_new_fs_root() to get the btrfs_root of that subvolume. The idea here is, we have | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26727 In the Linux kernel, the following vulnerability has been resolved: b ... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
GHSA-w9mj-34hr-82rj In the Linux kernel, the following vulnerability has been resolved: btrfs: do not ASSERT() if the newly created subvolume already got read [BUG] There is a syzbot crash, triggered by the ASSERT() during subvolume creation: assertion failed: !anon_dev, in fs/btrfs/disk-io.c:1319 ------------[ cut here ]------------ kernel BUG at fs/btrfs/disk-io.c:1319! invalid opcode: 0000 [#1] PREEMPT SMP KASAN RIP: 0010:btrfs_get_root_ref.part.0+0x9aa/0xa60 <TASK> btrfs_get_new_fs_root+0xd3/0xf0 create_subvol+0xd02/0x1650 btrfs_mksubvol+0xe95/0x12b0 __btrfs_ioctl_snap_create+0x2f9/0x4f0 btrfs_ioctl_snap_create+0x16b/0x200 btrfs_ioctl+0x35f0/0x5cf0 __x64_sys_ioctl+0x19d/0x210 do_syscall_64+0x3f/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b ---[ end trace 0000000000000000 ]--- [CAUSE] During create_subvol(), after inserting root item for the newly created subvolume, we would trigger btrfs_get_new_fs_root() to get the btrfs_root of that subvolume. The idea here is, we h... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
BDU:2024-08676 Уязвимость компонента btrfs ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | почти 3 года назад | |
ROS-20241021-09 Множественные уязвимости kernel-lt | CVSS3: 8.8 | около 2 лет назад | ||
SUSE-SU-2024:1641-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2024-2868 ALT-PU-2024-2868: package `kernel-image-un-def` update to version 6.1.79-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-18361 ALT-PU-2024-18361: package `kernel-image-std-def` update to version 6.1.79-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-3144 ALT-PU-2024-3144: package `kernel-image-rt` update to version 6.1.79-alt1.rt25 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-18464 ALT-PU-2024-18464: package `kernel-image-un-def` update to version 6.6.18-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-18207 ALT-PU-2024-18207: package `kernel-image-pine` update to version 6.6.18-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-3273 ALT-PU-2024-3273: package `kernel-image-rt` update to version 5.10.210-alt1.rt102 | CVSS3: 9.8 | больше 2 лет назад | ||
SUSE-SU-2024:1490-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2024-3457 ALT-PU-2024-3457: package `kernel-image-std-def` update to version 5.10.211-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
SUSE-SU-2024:1659-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:1663-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2024-3415 ALT-PU-2024-3415: package `kernel-image-mp` update to version 6.7.8-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-6818 ALT-PU-2024-6818: package `kernel-image-rpi-un` update to version 6.6.23-alt1 | CVSS3: 9.4 | больше 2 лет назад |
Уязвимостей на страницу