Количество 34
Количество 34
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 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
btrfs: wait for fixup workers before stopping cleaner kthread during umount
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-2025:03190-1
Security update for the Linux Kernel (Live Patch 17 for SLE 15 SP5)
SUSE-SU-2025:03181-1
Security update for the Linux Kernel (Live Patch 32 for SLE 15 SP4)
SUSE-SU-2025:03175-1
Security update for the Linux Kernel (Live Patch 29 for SLE 15 SP4)
SUSE-SU-2025:03156-1
Security update for the Linux Kernel (Live Patch 31 for SLE 15 SP4)
SUSE-SU-2025:03130-1
Security update for the Linux Kernel (Live Patch 47 for SLE 15 SP3)
SUSE-SU-2025:03124-1
Security update for the Linux Kernel (Live Patch 49 for SLE 15 SP3)
SUSE-SU-2025:03191-1
Security update for the Linux Kernel (Live Patch 20 for SLE 15 SP5)
SUSE-SU-2025:03186-1
Security update for the Linux Kernel (Live Patch 19 for SLE 15 SP5)
SUSE-SU-2025:03226-1
Security update for the Linux Kernel (Live Patch 5 for SLE 15 SP6)
SUSE-SU-2025:03223-1
Security update for the Linux Kernel (Live Patch 3 for SLE 15 SP6)
SUSE-SU-2025:03209-1
Security update for the Linux Kernel (Live Patch 4 for SLE 15 SP6)
SUSE-SU-2025:03108-1
Security update for the Linux Kernel RT (Live Patch 0 for SLE 15 SP6)
SUSE-SU-2025:03097-1
Security update for the Linux Kernel RT (Live Patch 1 for SLE 15 SP6)
Уязвимостей на страницу
Уязвимость | 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 resour... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
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% Низкий | около 1 года назад | |
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% Низкий | около 1 года назад | |
CVE-2024-49867 btrfs: wait for fixup workers before stopping cleaner kthread during umount | 0% Низкий | около 1 года назад | ||
CVE-2024-49867 In the Linux kernel, the following vulnerability has been resolved: b ... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
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% Низкий | около 1 года назад | |
BDU:2025-03126 Уязвимость функции close_ctree() (fs/btrfs/disk-io.c) ядра операционной системы Linux, позволяющая нарушителю повысить свои привилегии | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
SUSE-SU-2025:03190-1 Security update for the Linux Kernel (Live Patch 17 for SLE 15 SP5) | 2 месяца назад | |||
SUSE-SU-2025:03181-1 Security update for the Linux Kernel (Live Patch 32 for SLE 15 SP4) | 2 месяца назад | |||
SUSE-SU-2025:03175-1 Security update for the Linux Kernel (Live Patch 29 for SLE 15 SP4) | 2 месяца назад | |||
SUSE-SU-2025:03156-1 Security update for the Linux Kernel (Live Patch 31 for SLE 15 SP4) | 2 месяца назад | |||
SUSE-SU-2025:03130-1 Security update for the Linux Kernel (Live Patch 47 for SLE 15 SP3) | 2 месяца назад | |||
SUSE-SU-2025:03124-1 Security update for the Linux Kernel (Live Patch 49 for SLE 15 SP3) | 2 месяца назад | |||
SUSE-SU-2025:03191-1 Security update for the Linux Kernel (Live Patch 20 for SLE 15 SP5) | 2 месяца назад | |||
SUSE-SU-2025:03186-1 Security update for the Linux Kernel (Live Patch 19 for SLE 15 SP5) | 2 месяца назад | |||
SUSE-SU-2025:03226-1 Security update for the Linux Kernel (Live Patch 5 for SLE 15 SP6) | 2 месяца назад | |||
SUSE-SU-2025:03223-1 Security update for the Linux Kernel (Live Patch 3 for SLE 15 SP6) | 2 месяца назад | |||
SUSE-SU-2025:03209-1 Security update for the Linux Kernel (Live Patch 4 for SLE 15 SP6) | 2 месяца назад | |||
SUSE-SU-2025:03108-1 Security update for the Linux Kernel RT (Live Patch 0 for SLE 15 SP6) | 2 месяца назад | |||
SUSE-SU-2025:03097-1 Security update for the Linux Kernel RT (Live Patch 1 for SLE 15 SP6) | 2 месяца назад |
Уязвимостей на страницу