CVE-2024-56759

btrfs: fix use-after-free when COWing tree bock and tracing is enabled

HIGH
7.8
CVSS Score
Published: January 6, 2025 at 04:20 PM UTC
Updated: August 5, 2026 at 12:44 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix use-after-free when COWing tree bock and tracing is enabled When a COWing a tree block, at btrfs_cow_block(), and we have the tracepoint trace_btrfs_cow_block() enabled and preemption is also enabled (CONFIG_PREEMPT=y), we can trigger a use-after-free in the COWed extent buffer while inside the tracepoint code. This is because in some paths that call btrfs_cow_block(), such as btrfs_search_slot(), we are holding the last reference on the extent buffer @buf so btrfs_force_cow_block() drops the last reference on the @buf extent buffer when it calls free_extent_buffer_stale(buf), which schedules the release of the extent buffer with RCU. This means that if we are on a kernel with preemption, the current task may be preempted before calling trace_btrfs_cow_block() and the extent buffer already released by the time trace_btrfs_cow_block() is called, resulting in a use-after-free. Fix this by moving the trace_btrfs_cow_block() from btrfs_cow_block() to btrfs_force_cow_block() before the COWed extent buffer is freed. This also has a side effect of invoking the tracepoint in the tree defrag code, at defrag.c:btrfs_realloc_node(), since btrfs_force_cow_block() is called there, but this is fine and it was actually missing there.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 6.12.83.4 ≤ v < 5.10.2333.4 ≤ v < 5.15.1763.4 ≤ v < 6.1.1243.4 ≤ v < 6.12.83.4 ≤ v < 6.133.4 ≤ v < 6.6.703083ee2e18b701122a3b841db83448543a87a5836.13 rc16.13 rc26.13 rc36.13 rc4
Vendor states this is fixed in 44f52bbe96dfdbe4aca3818a2534520082a07040 (fixed)
Vendor states this is fixed in 526ff5b27f090fb15040471f892cd2c9899ce314 (fixed)
Vendor states this is fixed in 66376f1a73cba57fd0af2631d7888605b738e499 (fixed)
Vendor states this is fixed in 9a466b8693b9add05de99af00c7bdff8259ecf19 (fixed)
Vendor states this is fixed in ba5120a2fb5f23b4d39d302e181aa5d4e28a90d1 (fixed)
Vendor states this is fixed in c3a403d8ce36f5a809a492581de5ad17843e4701 (fixed)
Vendor states this is fixed in 3.4 (unaffected)
Vendor states this is fixed in 5.10.233 (unaffected)
Vendor states this is fixed in 5.15.176 (unaffected)
Vendor states this is fixed in 6.1.124 (unaffected)
Vendor states this is fixed in 6.12.8 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.6.70 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (8)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card