CVE-2026-90262

btrfs: retry verity reads for not-uptodate Merkle folios

N/A
Published: September 17, 2026 at 04:07 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

06ed09351b67eb1114ae106a87a0ee3ea9adb3db6.66ed9351b67eb1114ae106a87a0ee3ea9adb3db
Vendor states this is fixed in 12b6d1a1715cbced2e445ca353f9c9987b8636e2 (fixed)
Vendor states this is fixed in 81241f734f0f662378f5ffc53882b012923e6fe5 (fixed)
Vendor states this is fixed in 8cc569696dac51fc62bb39b3b8f530582b916d29 (fixed)
Vendor states this is fixed in 90e9eae1b5907fa36620ffb7f4f1a4afa9333427 (fixed)
Vendor states this is fixed in c1fa005cdf3b7ff14cdfd7d512830088a3fc256b (fixed)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card