{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "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.",
  "id": "DEBIAN-CVE-2026-90262",
  "modified": "2026-09-18T04:47:26.521961779Z",
  "published": "2026-09-17T17:17:22.640Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-90262"
    }
  ],
  "upstream": [
    "CVE-2026-90262"
  ]
}