CVE-2022-49761

linux: In the Linux kernel, the following vulnerability has been resolved: btrfs: always report error in run_one_delayed_re...

CVE-2022-49761 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-49761, released March 27, 2025. It is not reported as exploited. Patch Radar priority: High.

High
CVSS
7.8
high
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0020
9th percentile

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.

Where it's fixed

ProductFixed inFixReleased
Linux
linux · Debian 12.15 (bookworm) 6.1.8-1 DEBIAN-CVE-2022-49761 Mar 27, 2025
linux · Debian 13.5 (trixie) 6.1.8-1 DEBIAN-CVE-2022-49761 Mar 27, 2025
linux · Debian 14 6.1.8-1 DEBIAN-CVE-2022-49761 Mar 27, 2025

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.