CVE-2022-49167

published 26 Feb 2025 · updated 5 Aug 2026

btrfs: do not double complete bio on errors during compressed reads

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4a4ceb2b990771c374d85d496a1a45255dde48e3, Kernel 987b5df1d10355d377315a26e7fb6c72ded83c9f and Kernel f9f15de85d74e7eef021af059ca53a15f041cdd8.

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().

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.16, >=86ccbb4d2a2af4109430df518c995a4f7d14dfd2 <4a4ceb2b990771c374d85d496a1a45255dde48e3, >=86ccbb4d2a2af4109430df518c995a4f7d14dfd2 <987b5df1d10355d377315a26e7fb6c72ded83c9f, >=86ccbb4d2a2af4109430df518c995a4f7d14dfd2 <f9f15de85d74e7eef021af059ca53a15f041cdd84a4ceb2b990771c374d85d496a1a45255dde48e3, 987b5df1d10355d377315a26e7fb6c72ded83c9f, f9f15de85d74e7eef021af059ca53a15f041cdd8

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-49167 severity on Zeptric[![CVE-2022-49167](https://zeptric.io/badge/cve/CVE-2022-49167.svg)](https://zeptric.io/cve/CVE-2022-49167)