CVE-2022-49761

btrfs: always report error in run_one_delayed_ref()

State
Published
Severity
7.8 High
Published
Mar 27, 2025
Updated
May 11, 2026
Reserved
Mar 27, 2025

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCISA-ADP

Weaknesses

Affected Products

ProductVersions
LinuxLinux
  • 79787eaab46121d4713ed03c8fc63b9ec3eaec76 to before 18bd1c9c02e64a3567f90c83c2c8b855531c8098Affected
  • 79787eaab46121d4713ed03c8fc63b9ec3eaec76 to before fdb4a70bb768d2a87890409597529ad81cb3de8aAffected
  • 79787eaab46121d4713ed03c8fc63b9ec3eaec76 to before 853ffa1511b058c79a4c9bb1407b3b20ce311792Affected
  • 79787eaab46121d4713ed03c8fc63b9ec3eaec76 to before 39f501d68ec1ed5cd5c66ac6ec2a7131c517bb92Affected
LinuxLinux
  • 3.4Affected
  • before 3.4Not affected
  • 5.10.165 through 5.10.*Not affected
  • 5.15.90 through 5.15.*Not affected
  • 6.1.8 through 6.1.*Not affected
  • 6.2 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.