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

CVE-2024-49867
In the Linux kernel, the following vulnerability has been resolved: btrfs: wait for fixup workers before stopping cleaner kthread during umount During unmount, at close_ctree(), we have the following steps in this order: 1) Park the cleaner kthread - this doesn't destroy the kthread, it basically halts its execution (wake ups against it work but do nothing); 2) We stop the cleaner kthread - this results in freeing the respective struct task_struct; 3) We call btrfs_stop_all_workers() which waits for any jobs running in all the work queues and then free the work queues. Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don't wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free all its ...

CVE-2024-49867
In the Linux kernel, the following vulnerability has been resolved: btrfs: wait for fixup workers before stopping cleaner kthread during umount During unmount, at close_ctree(), we have the following steps in this order: 1) Park the cleaner kthread - this doesn't destroy the kthread, it basically halts its execution (wake ups against it work but do nothing); 2) We stop the cleaner kthread - this results in freeing the respective struct task_struct; 3) We call btrfs_stop_all_workers() which waits for any jobs running in all the work queues and then free the work queues. Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don't wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free all its resour...

CVE-2024-49867
In the Linux kernel, the following vulnerability has been resolved: btrfs: wait for fixup workers before stopping cleaner kthread during umount During unmount, at close_ctree(), we have the following steps in this order: 1) Park the cleaner kthread - this doesn't destroy the kthread, it basically halts its execution (wake ups against it work but do nothing); 2) We stop the cleaner kthread - this results in freeing the respective struct task_struct; 3) We call btrfs_stop_all_workers() which waits for any jobs running in all the work queues and then free the work queues. Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don't wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free al

CVE-2024-49867
CVE-2024-49867
In the Linux kernel, the following vulnerability has been resolved: b ...
GHSA-h7p9-f9r3-6533
In the Linux kernel, the following vulnerability has been resolved: btrfs: wait for fixup workers before stopping cleaner kthread during umount During unmount, at close_ctree(), we have the following steps in this order: 1) Park the cleaner kthread - this doesn't destroy the kthread, it basically halts its execution (wake ups against it work but do nothing); 2) We stop the cleaner kthread - this results in freeing the respective struct task_struct; 3) We call btrfs_stop_all_workers() which waits for any jobs running in all the work queues and then free the work queues. Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don't wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free...

BDU:2025-03126
Уязвимость функции close_ctree() (fs/btrfs/disk-io.c) ядра операционной системы Linux, позволяющая нарушителю повысить свои привилегии

SUSE-SU-2024:4103-1
Security update for the Linux Kernel

SUSE-SU-2024:4140-1
Security update for the Linux Kernel

ROS-20250312-01
Множественные уязвимости kernel-lt

SUSE-SU-2025:0834-1
Security update for the Linux Kernel

SUSE-SU-2024:4131-1
Security update for the Linux Kernel
ELSA-2024-12884
ELSA-2024-12884: Unbreakable Enterprise kernel security update (IMPORTANT)

SUSE-SU-2024:3983-1
Security update for the Linux Kernel

SUSE-SU-2024:3985-1
Security update for the Linux Kernel
ELSA-2024-12887
ELSA-2024-12887: Unbreakable Enterprise kernel security update (IMPORTANT)

SUSE-SU-2024:3986-1
Security update for the Linux Kernel

SUSE-SU-2024:3984-1
Security update for the Linux Kernel

SUSE-SU-2024:4364-1
Security update for the Linux Kernel

SUSE-SU-2024:4387-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
---|---|---|---|---|
![]() | CVE-2024-49867 In the Linux kernel, the following vulnerability has been resolved: btrfs: wait for fixup workers before stopping cleaner kthread during umount During unmount, at close_ctree(), we have the following steps in this order: 1) Park the cleaner kthread - this doesn't destroy the kthread, it basically halts its execution (wake ups against it work but do nothing); 2) We stop the cleaner kthread - this results in freeing the respective struct task_struct; 3) We call btrfs_stop_all_workers() which waits for any jobs running in all the work queues and then free the work queues. Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don't wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free all its ... | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад |
![]() | CVE-2024-49867 In the Linux kernel, the following vulnerability has been resolved: btrfs: wait for fixup workers before stopping cleaner kthread during umount During unmount, at close_ctree(), we have the following steps in this order: 1) Park the cleaner kthread - this doesn't destroy the kthread, it basically halts its execution (wake ups against it work but do nothing); 2) We stop the cleaner kthread - this results in freeing the respective struct task_struct; 3) We call btrfs_stop_all_workers() which waits for any jobs running in all the work queues and then free the work queues. Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don't wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free all its resour... | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад |
![]() | CVE-2024-49867 In the Linux kernel, the following vulnerability has been resolved: btrfs: wait for fixup workers before stopping cleaner kthread during umount During unmount, at close_ctree(), we have the following steps in this order: 1) Park the cleaner kthread - this doesn't destroy the kthread, it basically halts its execution (wake ups against it work but do nothing); 2) We stop the cleaner kthread - this results in freeing the respective struct task_struct; 3) We call btrfs_stop_all_workers() which waits for any jobs running in all the work queues and then free the work queues. Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don't wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free al | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад |
![]() | CVSS3: 5.5 | 0% Низкий | 7 месяцев назад | |
CVE-2024-49867 In the Linux kernel, the following vulnerability has been resolved: b ... | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад | |
GHSA-h7p9-f9r3-6533 In the Linux kernel, the following vulnerability has been resolved: btrfs: wait for fixup workers before stopping cleaner kthread during umount During unmount, at close_ctree(), we have the following steps in this order: 1) Park the cleaner kthread - this doesn't destroy the kthread, it basically halts its execution (wake ups against it work but do nothing); 2) We stop the cleaner kthread - this results in freeing the respective struct task_struct; 3) We call btrfs_stop_all_workers() which waits for any jobs running in all the work queues and then free the work queues. Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don't wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free... | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад | |
![]() | BDU:2025-03126 Уязвимость функции close_ctree() (fs/btrfs/disk-io.c) ядра операционной системы Linux, позволяющая нарушителю повысить свои привилегии | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад |
![]() | SUSE-SU-2024:4103-1 Security update for the Linux Kernel | 7 месяцев назад | ||
![]() | SUSE-SU-2024:4140-1 Security update for the Linux Kernel | 7 месяцев назад | ||
![]() | ROS-20250312-01 Множественные уязвимости kernel-lt | CVSS3: 7.8 | 3 месяца назад | |
![]() | SUSE-SU-2025:0834-1 Security update for the Linux Kernel | 3 месяца назад | ||
![]() | SUSE-SU-2024:4131-1 Security update for the Linux Kernel | 7 месяцев назад | ||
ELSA-2024-12884 ELSA-2024-12884: Unbreakable Enterprise kernel security update (IMPORTANT) | 6 месяцев назад | |||
![]() | SUSE-SU-2024:3983-1 Security update for the Linux Kernel | 7 месяцев назад | ||
![]() | SUSE-SU-2024:3985-1 Security update for the Linux Kernel | 7 месяцев назад | ||
ELSA-2024-12887 ELSA-2024-12887: Unbreakable Enterprise kernel security update (IMPORTANT) | 6 месяцев назад | |||
![]() | SUSE-SU-2024:3986-1 Security update for the Linux Kernel | 7 месяцев назад | ||
![]() | SUSE-SU-2024:3984-1 Security update for the Linux Kernel | 7 месяцев назад | ||
![]() | SUSE-SU-2024:4364-1 Security update for the Linux Kernel | 6 месяцев назад | ||
![]() | SUSE-SU-2024:4387-1 Security update for the Linux Kernel | 6 месяцев назад |
Уязвимостей на страницу