nday
CVE-2024-56581

btrfs: ref-verify: fix use-after-free after invalid ref action

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags weakness typeuse-after-free accesslocalno user interaction productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

use-after-free
CWE-416, stated by the ADP CISA-ADP, NVD's analysts, and NVD, republishing 134c704f-9b21-4f2e-91b3-4a467353bcc0
local
AV:L in CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
no user interaction
UI:N in CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
Linux kernel
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernel
operating system
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
7.0 HIGH v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2024-12-27T14:23Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

In the Linux kernel, the following vulnerability has been resolved:

btrfs: ref-verify: fix use-after-free after invalid ref action

At btrfs_ref_tree_mod() after we successfully inserted the new ref entry (local variable 'ref') into the respective block entry's rbtree (local variable 'be'), if we find an unexpected action of BTRFS_DROP_DELAYED_REF, we error out and free the ref entry without removing it from the block entry's rbtree. Then in the error path of btrfs_ref_tree_mod() we call btrfs_free_ref_cache(), which iterates over all block entries and then calls free_block_entry() for each one, and there we will trigger a use-after-free when we are called against the block entry to which we added the freed ref entry to its rbtree, since the rbtree still points to the block entry, as we didn't remove it from the rbtree before freeing it in the error path at btrfs_ref_tree_mod(). Fix this by removing the new ref entry from the rbtree before freeing it.

Syzbot report this with the following stack traces:

BTRFS error (device loop0 state EA):   Ref action 2, root 5, ref_root 0, parent 8564736, owner 0, offset 0, num_refs 18446744073709551615
   __btrfs_mod_ref+0x7dd/0xac0 fs/btrfs/extent-tree.c:2523
   update_ref_for_cow+0x9cd/0x11f0 fs/btrfs/ctree.c:512
   btrfs_force_cow_block+0x9f6/0x1da0 fs/btrfs/ctree.c:594
   btrfs_cow_block+0x35e/0xa40 fs/btrfs/ctree.c:754
   btrfs_search_slot+0xbdd/0x30d0 fs/btrfs/ctree.c:2116
   btrfs_insert_empty_items+0x9c/0x1a0 fs/btrfs/ctree.c:4314
   btrfs_insert_empty_item fs/btrfs/ctree.h:669 [inline]
   btrfs_insert_orphan_item+0x1f1/0x320 fs/btrfs/orphan.c:23
   btrfs_orphan_add+0x6d/0x1a0 fs/btrfs/inode.c:3482
   btrfs_unlink+0x267/0x350 fs/btrfs/inode.c:4293
   vfs_unlink+0x365/0x650 fs/namei.c:4469
   do_unlinkat+0x4ae/0x830 fs/namei.c:4533
   __do_sys_unlinkat fs/namei.c:4576 [inline]
   __se_sys_unlinkat fs/namei.c:4569 [inline]
   __x64_sys_unlinkat+0xcc/0xf0 fs/namei.c:4569
   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
BTRFS error (device loop0 state EA):   Ref action 1, root 5, ref_root 5, parent 0, owner 260, offset 0, num_refs 1
   __btrfs_mod_ref+0x76b/0xac0 fs/btrfs/extent-tree.c:2521
   update_ref_for_cow+0x96a/0x11f0
   btrfs_force_cow_block+0x9f6/0x1da0 fs/btrfs/ctree.c:594
   btrfs_cow_block+0x35e/0xa40 fs/btrfs/ctree.c:754
   btrfs_search_slot+0xbdd/0x30d0 fs/btrfs/ctree.c:2116
   btrfs_lookup_inode+0xdc/0x480 fs/btrfs/inode-item.c:411
   __btrfs_update_delayed_inode+0x1e7/0xb90 fs/btrfs/delayed-inode.c:1030
   btrfs_update_delayed_inode fs/btrfs/delayed-inode.c:1114 [inline]
   __btrfs_commit_inode_delayed_items+0x2318/0x24a0 fs/btrfs/delayed-inode.c:1137
   __btrfs_run_delayed_items+0x213/0x490 fs/btrfs/delayed-inode.c:1171
   btrfs_commit_transaction+0x8a8/0x3740 fs/btrfs/transaction.c:2313
   prepare_to_relocate+0x3c4/0x4c0 fs/btrfs/relocation.c:3586
   relocate_block_group+0x16c/0xd40 fs/btrfs/relocation.c:3611
   btrfs_relocate_block_group+0x77d/0xd90 fs/btrfs/relocation.c:4081
   btrfs_relocate_chunk+0x12c/0x3b0 fs/btrfs/volumes.c:3377
   __btrfs_balance+0x1b0f/0x26b0 fs/btrfs/volumes.c:4161
   btrfs_balance+0xbdc/0x10c0 fs/btrfs/volumes.c:4538
BTRFS error (device loop0 state EA):   Ref action 2, root 5, ref_root 0, parent 8564736, owner 0, offset 0, num_refs 18446744073709551615
   __btrfs_mod_ref+0x7dd/0xac0 fs/btrfs/extent-tree.c:2523
   update_ref_for_cow+0x9cd/0x11f0 fs/btrfs/ctree.c:512
   btrfs_force_cow_block+0x9f6/0x1da0 fs/btrfs/ctree.c:594
   btrfs_cow_block+0x35e/0xa40 fs/btrfs/ctree.c:754
   btrfs_search_slot+0xbdd/0x30d0 fs/btrfs/ctree.c:2116
   btrfs_lookup_inode+0xdc/0x480 fs/btrfs/inode-item.c:411
   __btrfs_update_delayed_inode+0x1e7/0xb90 fs/btrfs/delayed-inode.c:1030
   btrfs_update_delayed_i

---truncated---

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:H
High: success depends on conditions outside the attacker's control, such as gathering details of the target or winning a race
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA Linux.

Event log

+DISdisclosed

CVE record published by Linux. CVSS 7, high.

src cvelist · nday , bulk import · raw
{
  "id": 347733,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2024-56581",
  "occurred_at": "2024-12-27T14:23:23.193Z",
  "observed_at": "2026-11-13T05:38:45.966745Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 7,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2025-02-11T15:42:39.280771Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2024-12-27T14:23:23.193Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.