CVE-2024-49868: btrfs: fix a NULL pointer dereference when failed to start a new trasacntion
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.28% (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 1282f001cbf56e5dd6e90a18e205a566793f4be0, 37fee9c220b92c3b7bf22b51c51dde5364e7590b, 39356ec0e319ed07627b3a0f402d0608546509e6; 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.
Low priority for now. Upgrade to Linux Linux 1282f001cbf56e5dd6e90a18e205a566793f4be0, 37fee9c220b92c3b7bf22b51c51dde5364e7590b, 39356ec0e319ed07627b3a0f402d0608546509e6; 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: fix a NULL pointer dereference when failed to start a new trasacntion [BUG] Syzbot reported a NULL pointer dereference with the following crash: FAULT_INJECTION: forcing a failure. start_transaction+0x830/0x1670 fs/btrfs/transaction.c:676 prepare_to_relocate+0x31f/0x4c0 fs/btrfs/relocation.c:3642 relocate_block_group+0x169/0xd20 fs/btrfs/relocation.c:3678 ... BTRFS info (device loop0): balance: ended with status: -12 Oops: general protection fault, probably for non-canonical address 0xdffffc00000000cc: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000660-0x0000000000000667] RIP: 0010:btrfs_update_reloc_root+0x362/0xa80 fs/btrfs/relocation.c:926 Call Trace: <TASK> commit_fs_roots+0x2ee/0x720 fs/btrfs/transaction.c:1496 btrfs_commit_transaction+0xfaf/0x3740 fs/btrfs/transaction.c:2430 del_balance_item fs/btrfs/volumes.c:3678 [inline] reset_balance_state+0x25e/0x3c0 fs/btrfs/volumes.c:3742 btrfs_balance+0xead/0x10c0 fs/btrfs/volumes.c:4574 btrfs_ioctl_balance+0x493/0x7c0 fs/btrfs/ioctl.c:3673 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f [CAUSE] The allocation failure happens at the start_transaction() inside prepare_to_relocate(), and during the error handling we call unset_reloc_control(), which makes fs_info->balance_ctl to be NULL. Then we continue the error path cleanup in btrfs_balance() by calling reset_balance_state() which will call del_balance_item() to fully delete the balance item in the root tree. However during the small window between set_reloc_contrl() and unset_reloc_control(), we can have a subvolume tree update and created a reloc_root for that subvolume. Then we go into the final btrfs_commit_transaction() of del_balance_item(), and into btrfs_update_reloc_root() inside commit_fs_roots(). That function checks if fs_info->reloc_ctl is in the merge_reloc_tree stage, but since fs_info->reloc_ctl is NULL, it results a NULL pointer dereference. [FIX] Just add extra check on fs_info->reloc_ctl inside btrfs_update_reloc_root(), before checking fs_info->reloc_ctl->merge_reloc_tree. That DEAD_RELOC_TREE handling is to prevent further modification to the reloc tree during merge stage, but since there is no reloc_ctl at all, we do not need to bother that.
- Published
- Oct 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 21th percentile
- CWE
- CWE-476
Report tools
Action score
22
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.
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.
Is your version affected? Check itNoroxi 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 |
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
- 2.6.35affected
- 3fd0a5585eb98e074fb9934549c8d85c49756c0d and later · before 1282f001cbf56e5dd6e90a18e205a566793f4be0affected · git
- 3fd0a5585eb98e074fb9934549c8d85c49756c0d and later · before d73d48acf36f57362df7e4f9d76568168bf5e944affected · git
- 3fd0a5585eb98e074fb9934549c8d85c49756c0d and later · before 37fee9c220b92c3b7bf22b51c51dde5364e7590baffected · git
- 3fd0a5585eb98e074fb9934549c8d85c49756c0d and later · before d13249c0df7aab885acb149695f82c54c0822a70affected · git
- 3fd0a5585eb98e074fb9934549c8d85c49756c0d and later · before 7ad0c5868f2f0418619089513d95230c66cb7eb4affected · git
- 3fd0a5585eb98e074fb9934549c8d85c49756c0d and later · before dc02c1440705e3451abd1c2c8114a5c1bb188e9faffected · git
- 3fd0a5585eb98e074fb9934549c8d85c49756c0d and later · before 39356ec0e319ed07627b3a0f402d0608546509e6affected · git
- 3fd0a5585eb98e074fb9934549c8d85c49756c0d and later · before c3b47f49e83197e8dffd023ec568403bcdbb774baffected · git
- before 2.6.35not affected · semver
Affected versions · NVD (6)
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
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 |
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-49866Oct 21, 2024 · tracing/timerlat: Fix a race during cpuhp processing18Monitor
- ← EarlierCVE-2024-49867Oct 21, 2024 · btrfs: wait for fixup workers before stopping cleaner kthread during umount22Monitor
- Later →CVE-2024-49869Oct 21, 2024 · btrfs: send: fix buffer overflow detection when copying path to cache entry31Monitor
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 | 1282f001cbf56e5dd6e90a18e205a566793f4be0 | Vendor (CNA) |
| Linux Linux | 37fee9c220b92c3b7bf22b51c51dde5364e7590b | Vendor (CNA) |
| Linux Linux | 39356ec0e319ed07627b3a0f402d0608546509e6 | Vendor (CNA) |
| Linux Linux | 7ad0c5868f2f0418619089513d95230c66cb7eb4 | Vendor (CNA) |
| Linux Linux | c3b47f49e83197e8dffd023ec568403bcdbb774b | Vendor (CNA) |
| Linux Linux | d13249c0df7aab885acb149695f82c54c0822a70 | Vendor (CNA) |
| Linux Linux | d73d48acf36f57362df7e4f9d76568168bf5e944 | Vendor (CNA) |
| Linux Linux | dc02c1440705e3451abd1c2c8114a5c1bb188e9f | 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) |
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/37fee9c220b92c3b7bf22b51c51dde5364e7590b
- git.kernel.org/stable/c/39356ec0e319ed07627b3a0f402d0608546509e6
- git.kernel.org/stable/c/7ad0c5868f2f0418619089513d95230c66cb7eb4
- git.kernel.org/stable/c/c3b47f49e83197e8dffd023ec568403bcdbb774b
- git.kernel.org/stable/c/d13249c0df7aab885acb149695f82c54c0822a70
- git.kernel.org/stable/c/d73d48acf36f57362df7e4f9d76568168bf5e944
- git.kernel.org/stable/c/dc02c1440705e3451abd1c2c8114a5c1bb188e9f
- 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.