Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90262btrfs: retry verity reads for not-uptodate Merkle folios

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 06ed09351b67eb1114ae106a87a0ee3ea9adb3db – < 90e9eae1b5907fa36620ffb7f4f1a4afa9333427
    • affected 06ed09351b67eb1114ae106a87a0ee3ea9adb3db – < c1fa005cdf3b7ff14cdfd7d512830088a3fc256b
    • affected 06ed09351b67eb1114ae106a87a0ee3ea9adb3db – < 12b6d1a1715cbced2e445ca353f9c9987b8636e2
    • affected 06ed09351b67eb1114ae106a87a0ee3ea9adb3db – < 81241f734f0f662378f5ffc53882b012923e6fe5
    • affected 06ed09351b67eb1114ae106a87a0ee3ea9adb3db – < 8cc569696dac51fc62bb39b3b8f530582b916d29
  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90262 badge
[![CVE-2026-90262](https://cveledger.app/badge/CVE-2026-90262.svg)](https://cveledger.app/cve/CVE-2026-90262)

Record last updated .