BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2024-57896High confidence

btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 19 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.21% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 19 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

23 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 19 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.124-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2024-57896 · CSAF 2.0 · revision 72 · interimSUSE Product Security TeamCVE-2024-57896
262 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount During the unmount path, at close_ctree(), we first stop the cleaner kthread, using kthread_stop() which frees the associated task_struct, and then stop and destroy all the work queues. However after we stopped the cleaner we may still have a worker from the delalloc_workers queue running inode.c:submit_compressed_extents(), which calls btrfs_add_delayed_iput(), which in turn tries to wake up the cleaner kthread - which was already destroyed before, resulting in a use-after-free on the task_struct. Syzbot reported this with the following stack traces: BUG: KASAN: slab-use-after-free in __lock_acquire+0x78/0x2100 kernel/locking/lockdep.c:5089 Read of size 8 at addr ffff8880259d2818 by task kworker/u8:3/52 CPU: 1 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.13.0-rc1-syzkaller-00002-gcdd30ebb1b9f #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: btrfs-delalloc btrfs_work_helper Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0x169/0x550 mm/kasan/report.c:489 kasan_report+0x143/0x180 mm/kasan/report.c:602 __lock_acquire+0x78/0x2100 kernel/locking/lockdep.c:5089 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0xd5/0x120 kernel/locking/spinlock.c:162 class_raw_spinlock_irqsave_constructor include/linux/spinlock.h:551 [inline] try_to_wake_up+0xc2/0x1470 kernel/sched/core.c:4205 submit_compressed_extents+0xdf/0x16e0 fs/btrfs/inode.c:1615 run_ordered_work fs/btrfs/async-thread.c:288 [inline] btrfs_work_helper+0x96f/0xc40 fs/btrfs/async-thread.c:324 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3310 worker_thread+0x870/0xd30 kernel/workqueue.c:3391 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 Allocated by task 2: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 unpoison_slab_object mm/kasan/common.c:319 [inline] __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:345 kasan_slab_alloc include/linux/kasan.h:250 [inline] slab_post_alloc_hook mm/slub.c:4104 [inline] slab_alloc_node mm/slub.c:4153 [inline] kmem_cache_alloc_node_noprof+0x1d9/0x380 mm/slub.c:4205 alloc_task_struct_node kernel/fork.c:180 [inline] dup_task_struct+0x57/0x8c0 kernel/fork.c:1113 copy_process+0x5d1/0x3d50 kernel/fork.c:2225 kernel_clone+0x223/0x870 kernel/fork.c:2807 kernel_thread+0x1bc/0x240 kernel/fork.c:2869 create_kthread kernel/kthread.c:412 [inline] kthreadd+0x60d/0x810 kernel/kthread.c:767 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 Freed by task 24: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:582 poison_slab_object mm/kasan/common.c:247 [inline] __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264 kasan_slab_free include/linux/kasan.h:233 [inline] slab_free_hook mm/slub.c:2338 [inline] slab_free mm/slub.c:4598 [inline] kmem_cache_free+0x195/0x410 mm/slub.c:4700 put_task_struct include/linux/sched/task.h:144 [inline] delayed_put_task_struct+0x125/0x300 kernel/exit.c:227 rcu_do_batch kernel/rcu/tree.c:2567 [inline] rcu_core+0xaaa/0x17a0 kernel/rcu/tree.c:2823 handle_softirqs+0x2d4/0x9b0 kernel/softirq.c:554 run_ksoftirqd+0xca/0x130 kernel/softirq.c:943 ---truncated---
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-53799

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 19 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount During the unmount path, at close_ctree(), we first stop the cleaner kthread, using kthread_stop() which frees the associated task_struct, and then stop and destroy all the work queues. However after we stopped the cleaner we may still have a worker from the delalloc_workers queue running inode.c:submit_compressed_extents(), which calls btrfs_add_delayed_iput(), which in turn tries to wake up the cleaner kthread - which was already destroyed before, resulting in a use-after-free on the task_struct. Syzbot reported this with the following stack traces: BUG: KASAN: slab-use-after-free in __lock_acquire+0x78/0x2100 kernel/locking/lockdep.c:5089 Read of size 8 at addr ffff8880259d2818 by task kworker/u8:3/52 CPU: 1 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.13.0-rc1-syzkaller-00002-gcdd30ebb1b9f #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: btrfs-delalloc btrfs_work_helper Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0x169/0x550 mm/kasan/report.c:489 kasan_report+0x143/0x180 mm/kasan/report.c:602 __lock_acquire+0x78/0x2100 kernel/locking/lockdep.c:5089 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0xd5/0x120 kernel/locking/spinlock.c:162 class_raw_spinlock_irqsave_constructor include/linux/spinlock.h:551 [inline] try_to_wake_up+0xc2/0x1470 kernel/sched/core.c:4205 submit_compressed_extents+0xdf/0x16e0 fs/btrfs/inode.c:1615 run_ordered_work fs/btrfs/async-thread.c:288 [inline] btrfs_work_helper+0x96f/0xc40 fs/btrfs/async-thread.c:324 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3310 worker_thread+0x870/0xd30 kernel/workqueue.c:3391 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> Allocated by task 2: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 unpoison_slab_object mm/kasan/common.c:319 [inline] __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:345 kasan_slab_alloc include/linux/kasan.h:250 [inline] slab_post_alloc_hook mm/slub.c:4104 [inline] slab_alloc_node mm/slub.c:4153 [inline] kmem_cache_alloc_node_noprof+0x1d9/0x380 mm/slub.c:4205 alloc_task_struct_node kernel/fork.c:180 [inline] dup_task_struct+0x57/0x8c0 kernel/fork.c:1113 copy_process+0x5d1/0x3d50 kernel/fork.c:2225 kernel_clone+0x223/0x870 kernel/fork.c:2807 kernel_thread+0x1bc/0x240 kernel/fork.c:2869 create_kthread kernel/kthread.c:412 [inline] kthreadd+0x60d/0x810 kernel/kthread.c:767 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 Freed by task 24: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:582 poison_slab_object mm/kasan/common.c:247 [inline] __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264 kasan_slab_free include/linux/kasan.h:233 [inline] slab_free_hook mm/slub.c:2338 [inline] slab_free mm/slub.c:4598 [inline] kmem_cache_free+0x195/0x410 mm/slub.c:4700 put_task_struct include/linux/sched/task.h:144 [inline] delayed_put_task_struct+0x125/0x300 kernel/exit.c:227 rcu_do_batch kernel/rcu/tree.c:2567 [inline] rcu_core+0xaaa/0x17a0 kernel/rcu/tree.c:2823 handle_softirqs+0x2d4/0x9b0 kernel/softirq.c:554 run_ksoftirqd+0xca/0x130 kernel/softirq.c:943 ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount During the unmount path, at close_ctree(), we first stop the cleaner kthread, using kthread_stop() which frees the associated task_struct, and then stop and destroy all the work queues. However after we stopped the cleaner we may still have a worker from the delalloc_workers queue running inode.c:submit_compressed_extents(), which calls btrfs_add_delayed_iput(), which in turn tries to wake up the cleaner kthread - which was already destroyed before, resulting in a use-after-free on the task_struct. Syzbot reported this with the following stack traces: BUG: KASAN: slab-use-after-free in __lock_acquire+0x78/0x2100 kernel/locking/lockdep.c:5089 Read of size 8 at addr ffff8880259d2818 by task kworker/u8:3/52 CPU: 1 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.13.0-rc1-syzkaller-00002-gcdd30ebb1b9f #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: btrfs-delalloc btrfs_work_helper Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0x169/0x550 mm/kasan/report.c:489 kasan_report+0x143/0x180 mm/kasan/report.c:602 __lock_acquire+0x78/0x2100 kernel/locking/lockdep.c:5089 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0xd5/0x120 kernel/locking/spinlock.c:162 class_raw_spinlock_irqsave_constructor include/linux/spinlock.h:551 [inline] try_to_wake_up+0xc2/0x1470 kernel/sched/core.c:4205 submit_compressed_extents+0xdf/0x16e0 fs/btrfs/inode.c:1615 run_ordered_work fs/btrfs/async-thread.c:288 [inline] btrfs_work_helper+0x96f/0xc40 fs/btrfs/async-thread.c:324 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3310 worker_thread+0x870/0xd30 kernel/workqueue.c:3391 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> Allocated by task 2: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 unpoison_slab_object mm/kasan/common.c:319 [inline] __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:345 kasan_slab_alloc include/linux/kasan.h:250 [inline] slab_post_alloc_hook mm/slub.c:4104 [inline] slab_alloc_node mm/slub.c:4153 [inline] kmem_cache_alloc_node_noprof+0x1d9/0x380 mm/slub.c:4205 alloc_task_struct_node kernel/fork.c:180 [inline] dup_task_struct+0x57/0x8c0 kernel/fork.c:1113 copy_process+0x5d1/0x3d50 kernel/fork.c:2225 kernel_clone+0x223/0x870 kernel/fork.c:2807 kernel_thread+0x1bc/0x240 kernel/fork.c:2869 create_kthread kernel/kthread.c:412 [inline] kthreadd+0x60d/0x810 kernel/kthread.c:767 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 Freed by task 24: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:582 poison_slab_object mm/kasan/common.c:247 [inline] __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264 kasan_slab_free include/linux/kasan.h:233 [inline] slab_free_hook mm/slub.c:2338 [inline] slab_free mm/slub.c:4598 [inline] kmem_cache_free+0x195/0x410 mm/slub.c:4700 put_task_struct include/linux/sched/task.h:144 [inline] delayed_put_task_struct+0x125/0x300 kernel/exit.c:227 rcu_do_batch kernel/rcu/tree.c:2567 [inline] rcu_core+0xaaa/0x17a0 kernel/rcu/tree.c:2823 handle_softirqs+0x2d4/0x9b0 kernel/softirq.c:554 run_ksoftirqd+0xca/0x130 kernel/softirq.c:943 ---truncated---

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount During the unmount path, at close_ctree(), we first stop the cleaner kthread, using kthread_stop() which frees the associated task_struct, and then stop and destroy all the work queues. However after we stopped the cleaner we may still have a worker from the delalloc_workers queue running inode.c:submit_compressed_extents(), which calls btrfs_add_delayed_iput(), which in turn tries to wake up the cleaner kthread - which was already destroyed before, resulting in a use-after-free on the task_struct. Syzbot reported this with the following stack traces: BUG: KASAN: slab-use-after-free in __lock_acquire+0x78/0x2100 kernel/locking/lockdep.c:5089 Read of size 8 at addr ffff8880259d2818 by task kworker/u8:3/52 CPU: 1 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.13.0-rc1-syzkaller-00002-gcdd30ebb1b9f #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: btrfs-delalloc btrfs_work_helper Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0x169/0x550 mm/kasan/report.c:489 kasan_report+0x143/0x180 mm/kasan/report.c:602 __lock_acquire+0x78/0x2100 kernel/locking/lockdep.c:5089 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0xd5/0x120 kernel/locking/spinlock.c:162 class_raw_spinlock_irqsave_constructor include/linux/spinlock.h:551 [inline] try_to_wake_up+0xc2/0x1470 kernel/sched/core.c:4205 submit_compressed_extents+0xdf/0x16e0 fs/btrfs/inode.c:1615 run_ordered_work fs/btrfs/async-thread.c:288 [inline] btrfs_work_helper+0x96f/0xc40 fs/btrfs/async-thread.c:324 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3310 worker_thread+0x870/0xd30 kernel/workqueue.c:3391 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> Allocated by task 2: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 unpoison_slab_object mm/kasan/common.c:319 [inline] __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:345 kasan_slab_alloc include/linux/kasan.h:250 [inline] slab_post_alloc_hook mm/slub.c:4104 [inline] slab_alloc_node mm/slub.c:4153 [inline] kmem_cache_alloc_node_noprof+0x1d9/0x380 mm/slub.c:4205 alloc_task_struct_node kernel/fork.c:180 [inline] dup_task_struct+0x57/0x8c0 kernel/fork.c:1113 copy_process+0x5d1/0x3d50 kernel/fork.c:2225 kernel_clone+0x223/0x870 kernel/fork.c:2807 kernel_thread+0x1bc/0x240 kernel/fork.c:2869 create_kthread kernel/kthread.c:412 [inline] kthreadd+0x60d/0x810 kernel/kthread.c:767 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 Freed by task 24: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:582 poison_slab_object mm/kasan/common.c:247 [inline] __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264 kasan_slab_free include/linux/kasan.h:233 [inline] slab_free_hook mm/slub.c:2338 [inline] slab_free mm/slub.c:4598 [inline] kmem_cache_free+0x195/0x410 mm/slub.c:4700 put_task_struct include/linux/sched/task.h:144 [inline] delayed_put_task_struct+0x125/0x300 kernel/exit.c:227 rcu_do_batch kernel/rcu/tree.c:2567 [inline] rcu_core+0xaaa/0x17a0 kernel/rcu/tree.c:2823 handle_softirqs+0x2d4/0x9b0 kernel/softirq.c:554 run_ksoftirqd+0xca/0x130 kernel/softirq.c:943 ---truncated---

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-416
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-0105Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250122Security Bulletin 22 Jan 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jan 2025, published on 22 January 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0366Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-57850 Référence CVE CVE-2024-57872 https://www.cve.org/CVERecord?id=CVE-2024-57872 Référence CVE CVE-2024-57874 https://www.cve.org/CVERecord?id=CVE-2024-57874 Référence CVE CVE-2024-57876 https://www.cve.org/CVERecord?id=CVE-2024-57876 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57884 https://www.cve.org/CVERecord?id=CVE-2024-57884 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=CVE-2024-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57900 https://www.cve.org/CVERecord?id=CVE-2024-57900 Référence CVE CVE-2024-57901 https://www.cve.org/CVERecord?id=CVE-2024-57901 Référence CVE CVE-2024-57902 https://www.cve.org/CVERecord?id=CVE-2024-57902 Référence CVE CVE-2024-57903 https://www.cve.org/CVERecord?id=CVE-2024-57903 Référence CVE CVE-2024-57904 https://www.cve.org/CVERecord?id=CVE-2024-57904 Référence CVE CVE-2024-57906 https://www.cve.org/CVERecord?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0349Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-57850 Référence CVE CVE-2024-57872 https://www.cve.org/CVERecord?id=CVE-2024-57872 Référence CVE CVE-2024-57874 https://www.cve.org/CVERecord?id=CVE-2024-57874 Référence CVE CVE-2024-57876 https://www.cve.org/CVERecord?id=CVE-2024-57876 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57884 https://www.cve.org/CVERecord?id=CVE-2024-57884 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=CVE-2024-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57900 https://www.cve.org/CVERecord?id=CVE-2024-57900 Référence CVE CVE-2024-57901 https://www.cve.org/CVERecord?id=CVE-2024-57901 Référence CVE CVE-2024-57902 https://www.cve.org/CVERecord?id=CVE-2024-57902 Référence CVE CVE-2024-57903 https://www.cve.org/CVERecord?id=CVE-2024-57903 Référence CVE CVE-2024-57904 https://www.cve.org/CVERecord?id=CVE-2024-57904 Référence CVE CVE-2024-57906 https://www.cve.org/CVERecord?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0308Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-57841 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57850 https://www.cve.org/CVERecord?id=CVE-2024-57850 Référence CVE CVE-2024-57874 https://www.cve.org/CVERecord?id=CVE-2024-57874 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57884 https://www.cve.org/CVERecord?id=CVE-2024-57884 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=CVE-2024-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57900 https://www.cve.org/CVERecord?id=CVE-2024-57900 Référence CVE CVE-2024-57901 https://www.cve.org/CVERecord?id=CVE-2024-57901 Référence CVE CVE-2024-57902 https://www.cve.org/CVERecord?id=CVE-2024-57902 Référence CVE CVE-2024-57903 https://www.cve.org/CVERecord?id=CVE-2024-57903 Référence CVE CVE-2024-57904 https://www.cve.org/CVERecord?id=CVE-2024-57904 Référence CVE CVE-2024-57906 https://www.cve.org/CVERecord?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0276Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-57841 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57850 https://www.cve.org/CVERecord?id=CVE-2024-57850 Référence CVE CVE-2024-57874 https://www.cve.org/CVERecord?id=CVE-2024-57874 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57884 https://www.cve.org/CVERecord?id=CVE-2024-57884 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=CVE-2024-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57900 https://www.cve.org/CVERecord?id=CVE-2024-57900 Référence CVE CVE-2024-57901 https://www.cve.org/CVERecord?id=CVE-2024-57901 Référence CVE CVE-2024-57902 https://www.cve.org/CVERecord?id=CVE-2024-57902 Référence CVE CVE-2024-57903 https://www.cve.org/CVERecord?id=CVE-2024-57903 Référence CVE CVE-2024-57904 https://www.cve.org/CVERecord?id=CVE-2024-57904 Référence CVE CVE-2024-57906 https://www.cve.org/CVERecord?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0254Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-57886 Référence CVE CVE-2024-57887 https://www.cve.org/CVERecord?id=CVE-2024-57887 Référence CVE CVE-2024-57888 https://www.cve.org/CVERecord?id=CVE-2024-57888 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=CVE-2024-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57893 https://www.cve.org/CVERecord?id=CVE-2024-57893 Référence CVE CVE-2024-57894 https://www.cve.org/CVERecord?id=CVE-2024-57894 Référence CVE CVE-2024-57895 https://www.cve.org/CVERecord?id=CVE-2024-57895 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57898 https://www.cve.org/CVERecord?id=CVE-2024-57898 Référence CVE CVE-2024-57899 https://www.cve.org/CVERecord?id=CVE-2024-57899 Référence CVE CVE-2024-57900 https://www.cve.org/CVERecord?id=CVE-2024-57900 Référence CVE CVE-2024-57901 https://www.cve.org/CVERecord?id=CVE-2024-57901 Référence CVE CVE-2024-57902 https://www.cve.org/CVERecord?id=CVE-2024-57902 Référence CVE CVE-2024-57903 https://www.cve.org/CVERecord?id=CVE-2024-57903 Référence CVE CVE-2024-57904 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0212Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-57792 Référence CVE CVE-2024-57793 https://www.cve.org/CVERecord?id=CVE-2024-57793 Référence CVE CVE-2024-57798 https://www.cve.org/CVERecord?id=CVE-2024-57798 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57850 https://www.cve.org/CVERecord?id=CVE-2024-57850 Référence CVE CVE-2024-57876 https://www.cve.org/CVERecord?id=CVE-2024-57876 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57893 https://www.cve.org/CVERecord?id=CVE-2024-57893 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57948 https://www.cve.org/CVERecord?id=CVE-2024-57948 Référence CVE CVE-2024-57979 https://www.cve.org/CVERecord?id=CVE-2024-57979 Référence CVE CVE-2024-57994 https://www.cve.org/CVERecord?id=CVE-2024-57994 Référence CVE CVE-2024-8805 https://www.cve.org/CVERecord?id=CVE-2024-8805 Référence CVE CVE-2025-21636 https://www.cve.org/CVERecord?id=CVE-2025-21636 Référence CVE CVE-2025-21637 https://www.cve.org/CVERecord?id=CVE-2025-21637 Référence CVE CVE-2025-21638 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0184Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2024-57876 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57884 https://www.cve.org/CVERecord?id=CVE-2024-57884 Référence CVE CVE-2024-57887 https://www.cve.org/CVERecord?id=CVE-2024-57887 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=CVE-2024-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57893 https://www.cve.org/CVERecord?id=CVE-2024-57893 Référence CVE CVE-2024-57894 https://www.cve.org/CVERecord?id=CVE-2024-57894 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57900 https://www.cve.org/CVERecord?id=CVE-2024-57900 Référence CVE CVE-2024-57901 https://www.cve.org/CVERecord?id=CVE-2024-57901 Référence CVE CVE-2024-57902 https://www.cve.org/CVERecord?id=CVE-2024-57902 Référence CVE CVE-2024-57903 https://www.cve.org/CVERecord?id=CVE-2024-57903 Référence CVE CVE-2024-57904 https://www.cve.org/CVERecord?id=CVE-2024-57904 Référence CVE CVE-2024-57906 https://www.cve.org/CVERecord?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0151Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-57874 Référence CVE CVE-2024-57876 https://www.cve.org/CVERecord?id=CVE-2024-57876 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57884 https://www.cve.org/CVERecord?id=CVE-2024-57884 Référence CVE CVE-2024-57887 https://www.cve.org/CVERecord?id=CVE-2024-57887 Référence CVE CVE-2024-57888 https://www.cve.org/CVERecord?id=CVE-2024-57888 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=CVE-2024-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57893 https://www.cve.org/CVERecord?id=CVE-2024-57893 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57899 https://www.cve.org/CVERecord?id=CVE-2024-57899 Référence CVE CVE-2024-57903 https://www.cve.org/CVERecord?id=CVE-2024-57903 Référence CVE CVE-2024-57904 https://www.cve.org/CVERecord?id=CVE-2024-57904 Référence CVE CVE-2024-57906 https://www.cve.org/CVERecord?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=CVE-2024-57907 Référence CVE CVE-2024-57908 https://www.cve.org/CVERecord?id=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0133Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-57874 Référence CVE CVE-2024-57876 https://www.cve.org/CVERecord?id=CVE-2024-57876 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57884 https://www.cve.org/CVERecord?id=CVE-2024-57884 Référence CVE CVE-2024-57887 https://www.cve.org/CVERecord?id=CVE-2024-57887 Référence CVE CVE-2024-57888 https://www.cve.org/CVERecord?id=CVE-2024-57888 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=CVE-2024-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57893 https://www.cve.org/CVERecord?id=CVE-2024-57893 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57899 https://www.cve.org/CVERecord?id=CVE-2024-57899 Référence CVE CVE-2024-57903 https://www.cve.org/CVERecord?id=CVE-2024-57903 Référence CVE CVE-2024-57904 https://www.cve.org/CVERecord?id=CVE-2024-57904 Référence CVE CVE-2024-57906 https://www.cve.org/CVERecord?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=CVE-2024-57907 Référence CVE CVE-2024-57908 https://www.cve.org/CVERecord?id=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0088Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-57850 Référence CVE CVE-2024-57857 https://www.cve.org/CVERecord?id=CVE-2024-57857 Référence CVE CVE-2024-57874 https://www.cve.org/CVERecord?id=CVE-2024-57874 Référence CVE CVE-2024-57876 https://www.cve.org/CVERecord?id=CVE-2024-57876 Référence CVE CVE-2024-57887 https://www.cve.org/CVERecord?id=CVE-2024-57887 Référence CVE CVE-2024-57888 https://www.cve.org/CVERecord?id=CVE-2024-57888 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=CVE-2024-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57893 https://www.cve.org/CVERecord?id=CVE-2024-57893 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57899 https://www.cve.org/CVERecord?id=CVE-2024-57899 Référence CVE CVE-2024-57903 https://www.cve.org/CVERecord?id=CVE-2024-57903 Référence CVE CVE-2024-57904 https://www.cve.org/CVERecord?id=CVE-2024-57904 Référence CVE CVE-2024-57906 https://www.cve.org/CVERecord?id=CVE-2024-57906 Référence CVE CVE-2024-57907 https://www.cve.org/CVERecord?id=CVE-2024-57907 Référence CVE CVE-2024-57908 https://www.cve.org/CVERecord?id=CVE-2024-57908 Référence CVE CVE-2024-57910 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-017218Linux の Linux Kernel における解放済みメモリの使用に関する脆弱性

Linux の Linux Kernel には、解放済みメモリの使用に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.0, 5.10.233 ≤ 5.10.*, 5.15.176 ≤ 5.15.*, 6.1.124 ≤ 6.1.*, 6.6.70 ≤ 6.6.*, 6.12.9 ≤ 6.12.*, 6.13 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 15 Jan 2025 · Last source change 5 Aug 2026, 11:46 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-53799
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-57896 · cve.blacktree.nl