CVE-2022-49167
btrfs: do not double complete bio on errors during compressed reads
Description
In the Linux kernel, the following vulnerability has been resolved: btrfs: do not double complete bio on errors during compressed reads I hit some weird panics while fixing up the error handling from btrfs_lookup_bio_sums(). Turns out the compression path will complete the bio we use if we set up any of the compression bios and then return an error, and then btrfs_submit_data_bio() will also call bio_endio() on the bio. Fix this by making btrfs_submit_compressed_read() responsible for calling bio_endio() on the bio if there are any errors. Currently it was only doing it if we created the compression bios, otherwise it was depending on btrfs_submit_data_bio() to do the right thing. This creates the above problem, so fix up btrfs_submit_compressed_read() to always call bio_endio() in case of an error, and then simply return from btrfs_submit_data_bio() if we had to call btrfs_submit_compressed_read().
INFO
Published Date :
Feb. 26, 2025, 7 a.m.
Last Modified :
Oct. 21, 2025, 5:13 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source | 
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] | 
Solution
- Update the Linux kernel to the latest version.
- Apply the patch for btrfs error handling.
- Recompile and deploy the kernel.
References to Advisories, Solutions, and Tools
                                            Here, you will find a curated list of external links that provide in-depth
                                            information, practical solutions, and valuable tools related to
                                            CVE-2022-49167.
                                        
CWE - Common Weakness Enumeration
            While CVE identifies
            specific instances of vulnerabilities, CWE categorizes the common flaws or
            weaknesses that can lead to vulnerabilities. CVE-2022-49167 is
            associated with the following CWEs:
        
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
            (CAPEC)
            stores attack patterns, which are descriptions of the common attributes and
            approaches employed by adversaries to exploit the CVE-2022-49167
            weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
			The following list is the news that have been mention
			CVE-2022-49167 vulnerability anywhere in the article.
		
                The following table lists the changes that have been made to the
                CVE-2022-49167 vulnerability over time.
            
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
- 
                            Initial Analysis by [email protected]Oct. 21, 2025 Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Added CWE NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.17 up to (excluding) 5.17.2 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 5.16.19 Added Reference Type kernel.org: https://git.kernel.org/stable/c/4a4ceb2b990771c374d85d496a1a45255dde48e3 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/987b5df1d10355d377315a26e7fb6c72ded83c9f Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/f9f15de85d74e7eef021af059ca53a15f041cdd8 Types: Patch 
- 
                            New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67Feb. 26, 2025 Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: btrfs: do not double complete bio on errors during compressed reads I hit some weird panics while fixing up the error handling from btrfs_lookup_bio_sums(). Turns out the compression path will complete the bio we use if we set up any of the compression bios and then return an error, and then btrfs_submit_data_bio() will also call bio_endio() on the bio. Fix this by making btrfs_submit_compressed_read() responsible for calling bio_endio() on the bio if there are any errors. Currently it was only doing it if we created the compression bios, otherwise it was depending on btrfs_submit_data_bio() to do the right thing. This creates the above problem, so fix up btrfs_submit_compressed_read() to always call bio_endio() in case of an error, and then simply return from btrfs_submit_data_bio() if we had to call btrfs_submit_compressed_read(). Added Reference https://git.kernel.org/stable/c/4a4ceb2b990771c374d85d496a1a45255dde48e3 Added Reference https://git.kernel.org/stable/c/987b5df1d10355d377315a26e7fb6c72ded83c9f Added Reference https://git.kernel.org/stable/c/f9f15de85d74e7eef021af059ca53a15f041cdd8 
 
                         
                         
                         
                                             
                                            