btrfs: retry verity reads for not-uptodate Merkle folios (CVE-2026-90262) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-90262

btrfs: retry verity reads for not-uptodate Merkle folios

Answer in brief

CVE-2026-90262 records a Unknown severity vulnerability in btrfs: retry verity reads for not-uptodate Merkle folios. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=06ed09351b67eb1114ae106a87a0ee3ea9adb3db <90e9eae1b5907fa36620ffb7f4f1a4afa9333427 \|\| >=06ed09351b67eb1114ae106a87a0ee3ea9adb3db <c1fa005cdf3b7ff14cdfd7d512830088a3fc256b \|\| >=06ed09351b67eb1114ae106a87a0ee3ea9adb3db <12b6d1a1715cbced2e445ca353f9c9987b8636e2 \|\| >=06ed09351b67eb1114ae106a87a0ee3ea9adb3db <81241f734f0f662378f5ffc53882b012923e6fe5 \|\| >=06ed09351b67eb1114ae106a87a0ee3ea9adb3db <8cc569696dac51fc62bb39b3b8f530582b916d29	90e9eae1b5907fa36620ffb7f4f1a4afa9333427, c1fa005cdf3b7ff14cdfd7d512830088a3fc256b, 12b6d1a1715cbced2e445ca353f9c9987b8636e2, 81241f734f0f662378f5ffc53882b012923e6fe5, 8cc569696dac51fc62bb39b3b8f530582b916d29
Linux/Linuxgeneric	6.6	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 90e9eae1b5907fa36620ffb7f4f1a4afa9333427 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.