btrfs: retry verity reads for not-uptodate Merkle folios
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 12b6d1a1715cbced2e445ca353f9c9987b8636e2, Kernel 81241f734f0f662378f5ffc53882b012923e6fe5, Kernel 8cc569696dac51fc62bb39b3b8f530582b916d29 and 2 more.
In the Linux kernel, the following vulnerability has been resolved: btrfs: retry verity reads for not-uptodate Merkle folios btrfs_read_merkle_tree_page() can find a folio in the mapping that is not uptodate. After taking the folio lock, the current code treats that state as a read error and returns -EIO. That can make a previous transient read failure sticky. If the failed read left a not-uptodate folio in the mapping, later callers find that folio and fail instead of retrying the read. Keep the existing page-cache insertion and locking order, but retry the Merkle item read when a not-uptodate folio is found in the mapping. Also unlock the folio when read_key_bytes() fails so that a later caller can lock it and retry the read.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.6, >=06ed09351b67eb1114ae106a87a0ee3ea9adb3db <12b6d1a1715cbced2e445ca353f9c9987b8636e2, >=06ed09351b67eb1114ae106a87a0ee3ea9adb3db <81241f734f0f662378f5ffc53882b012923e6fe5, >=06ed09351b67eb1114ae106a87a0ee3ea9adb3db <8cc569696dac51fc62bb39b3b8f530582b916d29, >=06ed09351b67eb1114ae106a87a0ee3ea9adb3db <90e9eae1b5907fa36620ffb7f4f1a4afa9333427, >=06ed09351b67eb1114ae106a87a0ee3ea9adb3db <c1fa005cdf3b7ff14cdfd7d512830088a3fc256b | 12b6d1a1715cbced2e445ca353f9c9987b8636e2, 81241f734f0f662378f5ffc53882b012923e6fe5, 8cc569696dac51fc62bb39b3b8f530582b916d29, 90e9eae1b5907fa36620ffb7f4f1a4afa9333427, c1fa005cdf3b7ff14cdfd7d512830088a3fc256b |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket