CVE-2022-49761

btrfs: always report error in run_one_delayed_ref()

HIGH
7.8
CVSS Score
Published: March 27, 2025 at 04:43 PM UTC
Updated: June 17, 2026 at 05:19 AM 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: always report error in run_one_delayed_ref() Currently we have a btrfs_debug() for run_one_delayed_ref() failure, but if end users hit such problem, there will be no chance that btrfs_debug() is enabled. This can lead to very little useful info for debugging. This patch will: - Add extra info for error reporting Including: * logical bytenr * num_bytes * type * action * ref_mod - Replace the btrfs_debug() with btrfs_err() - Move the error reporting into run_one_delayed_ref() This is to avoid use-after-free, the @node can be freed in the caller. This error should only be triggered at most once. As if run_one_delayed_ref() failed, we trigger the error message, then causing the call chain to error out: btrfs_run_delayed_refs() `- btrfs_run_delayed_refs() `- btrfs_run_delayed_refs_for_head() `- run_one_delayed_ref() And we will abort the current transaction in btrfs_run_delayed_refs(). If we have to run delayed refs for the abort transaction, run_one_delayed_ref() will just cleanup the refs and do nothing, thus no new error messages would be output.

Affected

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

v < 5.10.1653.4 ≤ v < 5.10.1653.4 ≤ v < 5.15.903.4 ≤ v < 6.1.83.4 ≤ v < 6.25.11 ≤ v < 5.15.905.16 ≤ v < 6.1.86.2 rc16.2 rc279787eaab46121d4713ed03c8fc63b9ec3eaec76
Vendor states this is fixed in 18bd1c9c02e64a3567f90c83c2c8b855531c8098 (fixed)
Vendor states this is fixed in 39f501d68ec1ed5cd5c66ac6ec2a7131c517bb92 (fixed)
Vendor states this is fixed in 853ffa1511b058c79a4c9bb1407b3b20ce311792 (fixed)
Vendor states this is fixed in fdb4a70bb768d2a87890409597529ad81cb3de8a (fixed)
Vendor states this is fixed in 3.4 (unaffected)
Vendor states this is fixed in 5.10.165 (unaffected)
Vendor states this is fixed in 5.15.90 (unaffected)
Vendor states this is fixed in 6.1.8 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/18bd1c9c02e64a3567f90c83c2c8b855531c8098
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/39f501d68ec1ed5cd5c66ac6ec2a7131c517bb92
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/853ffa1511b058c79a4c9bb1407b3b20ce311792
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/fdb4a70bb768d2a87890409597529ad81cb3de8a

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

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

CVSS

7.8HIGHCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
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