CVE-2024-49867: btrfs: wait for fixup workers before stopping cleaner kthread during umount
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.29% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 41fd1e94066a815a7ab0a7025359e9b40e4b3576, 4c98fe0dfa2ae83c4631699695506d8941db4bfe, 5.4.285; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.57.1-2; azl3 kernel 6.6.57.1-2 on Azure Linux 3.0 6.6.57.1-2.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 41fd1e94066a815a7ab0a7025359e9b40e4b3576, 4c98fe0dfa2ae83c4631699695506d8941db4bfe, 5.4.285; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.57.1-2; azl3 kernel 6.6.57.1-2 on Azure Linux 3.0 6.6.57.1-2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 resources. Fix this by waiting for any fixup workers at close_ctree() before we call kthread_stop() against the cleaner and run pending delayed iputs. The stack traces reported by syzbot were the following: BUG: KASAN: slab-use-after-free in __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065 Read of size 8 at addr ffff8880272a8a18 by task kworker/u8:3/52 CPU: 1 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.12.0-rc1-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: btrfs-fixup 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:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825 __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+0xb0/0x1480 kernel/sched/core.c:4154 btrfs_writepage_fixup_worker+0xc16/0xdf0 fs/btrfs/inode.c:2842 btrfs_work_helper+0x390/0xc50 fs/btrfs/async-thread.c:314 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa63/0x1850 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:247 [inline] slab_post_alloc_hook mm/slub.c:4086 [inline] slab_alloc_node mm/slub.c:4135 [inline] kmem_cache_alloc_node_noprof+0x16b/0x320 mm/slub.c:4187 alloc_task_struct_node kernel/fork.c:180 [inline] dup_task_struct+0x57/0x8c0 kernel/fork.c:1107 copy_process+0x5d1/0x3d50 kernel/fork.c:2206 kernel_clone+0x223/0x880 kernel/fork.c:2787 kernel_thread+0x1bc/0x240 kernel/fork.c:2849 create_kthread kernel/kthread.c:412 [inline] kthreadd+0x60d/0x810 kernel/kthread.c:765 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 61: 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:579 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:230 [inline] slab_free_h ---truncated---
- BDU:2025-03126
- SUSE-SU-2025:03097-1
- SUSE-SU-2025:03108-1
- SUSE-SU-2025:03124-1
- SUSE-SU-2025:03130-1
- SUSE-SU-2025:03156-1
- SUSE-SU-2025:03175-1
- SUSE-SU-2025:03181-1
- SUSE-SU-2025:03186-1
- SUSE-SU-2025:03190-1
- SUSE-SU-2025:03191-1
- SUSE-SU-2025:03209-1
- SUSE-SU-2025:03223-1
- SUSE-SU-2025:03226-1
- SUSE-SU-2025:20698-1
- SUSE-SU-2025:20703-1
- SUSE-SU-2025:20711-1
- SUSE-SU-2025:20714-1
- SUSE-SU-2025:20766-1
- SUSE-SU-2025:20782-1
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 22th percentile
- CWE
- CWE-416
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 5.10.227
- linux linux kernel5.11 and later · before 5.15.168
- linux linux kernel5.16 and later · before 6.1.113
- linux linux kernel6.2 and later · before 6.6.55
- linux linux kernel6.7 and later · before 6.10.14
- linux linux kernel6.11 and later · before 6.11.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6026fd9da213daab95469356fe7fdcf29ae1a296, 5.6affected
- 7a97311de48d56af6db4c5819f95faf9b0b23b1a and later · before a71349b692ab34ea197949e13e3cc42570fe73d9affected · git
- f4b1363cae43fef7c86c993b7ca7fe7d546b3c68 and later · before 70b60c8d9b42763d6629e44f448aa5d8ae477d61affected · git
- f4b1363cae43fef7c86c993b7ca7fe7d546b3c68 and later · before 4c98fe0dfa2ae83c4631699695506d8941db4bfeaffected · git
- f4b1363cae43fef7c86c993b7ca7fe7d546b3c68 and later · before 9da40aea63f8769f28afb91aea0fac4cf6fbbb65affected · git
- f4b1363cae43fef7c86c993b7ca7fe7d546b3c68 and later · before ed87190e9d9c80aad220fb6b0b03a84d22e2c95baffected · git
- f4b1363cae43fef7c86c993b7ca7fe7d546b3c68 and later · before bf0de0f9a0544c11f96f93206da04ab87dcea1f4affected · git
- f4b1363cae43fef7c86c993b7ca7fe7d546b3c68 and later · before 65d11eb276836d49003a8060cf31fa2284ad1047affected · git
- f4b1363cae43fef7c86c993b7ca7fe7d546b3c68 and later · before 41fd1e94066a815a7ab0a7025359e9b40e4b3576affected · git
- 5.4.22 and later · before 5.4.285affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.115-1 | 6.1.115-1 |
| Debian:13 | linux | before 6.11.4-1 | 6.11.4-1 |
| SUSE:Linux Enterprise Live Patching 15 SP3 | kernel-livepatch-SLE15-SP3_Update_47 | before 17-150300.2.1 | 17-150300.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP3 | kernel-livepatch-SLE15-SP3_Update_49 | before 15-150300.2.1 | 15-150300.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_29 | before 16-150400.2.1 | 16-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_31 | before 14-150400.2.1 | 14-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_32 | before 14-150400.2.1 | 14-150400.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_17 | before 16-150500.2.1 | 16-150500.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_19 | before 14-150500.2.1 | 14-150500.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_20 | before 14-150500.2.1 | 14-150500.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_3 | before 20-150600.2.1 | 20-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_4 | before 16-150600.2.1 | 16-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_5 | before 15-150600.2.1 | 15-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_0 | before 21-150600.3.1 | 21-150600.3.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_1 | before 20-150600.2.1 | 20-150600.2.1 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0_Update_2 | before 11-1.1 | 11-1.1 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0_Update_3 | before 11-1.2 | 11-1.2 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0-RT_Update_2 | before 11-1.1 | 11-1.1 |
| SUSE:Linux Micro 6.0 | kernel-livepatch-MICRO-6-0-RT_Update_3 | before 11-1.2 | 11-1.2 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-49865Oct 21, 2024 · drm/xe/vm: move xa_alloc to prevent UAF31Monitor
- ← EarlierCVE-2024-49866Oct 21, 2024 · tracing/timerlat: Fix a race during cpuhp processing18Monitor
- Later →CVE-2024-49868Oct 21, 2024 · btrfs: fix a NULL pointer dereference when failed to start a new trasacntion22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 41fd1e94066a815a7ab0a7025359e9b40e4b3576 | Vendor (CNA) |
| Linux Linux | 4c98fe0dfa2ae83c4631699695506d8941db4bfe | Vendor (CNA) |
| Linux Linux | 5.4.285 | Vendor (CNA) |
| Linux Linux | 5.6 | Vendor (CNA) |
| Linux Linux | 65d11eb276836d49003a8060cf31fa2284ad1047 | Vendor (CNA) |
| Linux Linux | 70b60c8d9b42763d6629e44f448aa5d8ae477d61 | Vendor (CNA) |
| Linux Linux | 9da40aea63f8769f28afb91aea0fac4cf6fbbb65 | Vendor (CNA) |
| Linux Linux | a71349b692ab34ea197949e13e3cc42570fe73d9 | Vendor (CNA) |
| Linux Linux | bf0de0f9a0544c11f96f93206da04ab87dcea1f4 | Vendor (CNA) |
| Linux Linux | ed87190e9d9c80aad220fb6b0b03a84d22e2c95b | Vendor (CNA) |
| azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 | 6.6.57.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.57.1-2 on Azure Linux 3.0 | 6.6.57.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.115-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP3_Update_47 | 17-150300.2.1 · SUSE:Linux Enterprise Live Patching 15 SP3 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP3_Update_49 | 15-150300.2.1 · SUSE:Linux Enterprise Live Patching 15 SP3 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP4_Update_29 | 16-150400.2.1 · SUSE:Linux Enterprise Live Patching 15 SP4 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP4_Update_31 | 14-150400.2.1 · SUSE:Linux Enterprise Live Patching 15 SP4 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP4_Update_32 | 14-150400.2.1 · SUSE:Linux Enterprise Live Patching 15 SP4 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5_Update_17 | 16-150500.2.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5_Update_19 | 14-150500.2.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5_Update_20 | 14-150500.2.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6_Update_3 | 20-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6_Update_4 | 16-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_0 | 21-150600.3.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_1 | 20-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/4c98fe0dfa2ae83c4631699695506d8941db4bfe
- git.kernel.org/stable/c/65d11eb276836d49003a8060cf31fa2284ad1047
- git.kernel.org/stable/c/70b60c8d9b42763d6629e44f448aa5d8ae477d61
- git.kernel.org/stable/c/9da40aea63f8769f28afb91aea0fac4cf6fbbb65
- git.kernel.org/stable/c/a71349b692ab34ea197949e13e3cc42570fe73d9
- git.kernel.org/stable/c/bf0de0f9a0544c11f96f93206da04ab87dcea1f4
- git.kernel.org/stable/c/ed87190e9d9c80aad220fb6b0b03a84d22e2c95b
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.