{"api_version":"1","generated_at":"2026-09-19T17:53:54+00:00","cve":"CVE-2026-90262","urls":{"html":"https://cve.report/CVE-2026-90262","api":"https://cve.report/api/cve/CVE-2026-90262.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-90262","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-90262"},"summary":{"title":"btrfs: retry verity reads for not-uptodate Merkle folios","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: retry verity reads for not-uptodate Merkle folios\n\nbtrfs_read_merkle_tree_page() can find a folio in the mapping that is not\nuptodate.  After taking the folio lock, the current code treats that state\nas a read error and returns -EIO.\n\nThat can make a previous transient read failure sticky.  If the failed read\nleft a not-uptodate folio in the mapping, later callers find that folio and\nfail instead of retrying the read.\n\nKeep the existing page-cache insertion and locking order, but retry the\nMerkle item read when a not-uptodate folio is found in the mapping.  Also\nunlock the folio when read_key_bytes() fails so that a later caller can\nlock it and retry the read.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-17 17:17:22","updated_at":"2026-09-17 17:17:22"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/90e9eae1b5907fa36620ffb7f4f1a4afa9333427","name":"https://git.kernel.org/stable/c/90e9eae1b5907fa36620ffb7f4f1a4afa9333427","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/81241f734f0f662378f5ffc53882b012923e6fe5","name":"https://git.kernel.org/stable/c/81241f734f0f662378f5ffc53882b012923e6fe5","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/8cc569696dac51fc62bb39b3b8f530582b916d29","name":"https://git.kernel.org/stable/c/8cc569696dac51fc62bb39b3b8f530582b916d29","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c1fa005cdf3b7ff14cdfd7d512830088a3fc256b","name":"https://git.kernel.org/stable/c/c1fa005cdf3b7ff14cdfd7d512830088a3fc256b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/12b6d1a1715cbced2e445ca353f9c9987b8636e2","name":"https://git.kernel.org/stable/c/12b6d1a1715cbced2e445ca353f9c9987b8636e2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-90262","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90262","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 06ed09351b67eb1114ae106a87a0ee3ea9adb3db 90e9eae1b5907fa36620ffb7f4f1a4afa9333427 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 06ed09351b67eb1114ae106a87a0ee3ea9adb3db c1fa005cdf3b7ff14cdfd7d512830088a3fc256b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 06ed09351b67eb1114ae106a87a0ee3ea9adb3db 12b6d1a1715cbced2e445ca353f9c9987b8636e2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 06ed09351b67eb1114ae106a87a0ee3ea9adb3db 81241f734f0f662378f5ffc53882b012923e6fe5 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 06ed09351b67eb1114ae106a87a0ee3ea9adb3db 8cc569696dac51fc62bb39b3b8f530582b916d29 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.6","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.157 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.110 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.52 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.6 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/btrfs/verity.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"90e9eae1b5907fa36620ffb7f4f1a4afa9333427","status":"affected","version":"06ed09351b67eb1114ae106a87a0ee3ea9adb3db","versionType":"git"},{"lessThan":"c1fa005cdf3b7ff14cdfd7d512830088a3fc256b","status":"affected","version":"06ed09351b67eb1114ae106a87a0ee3ea9adb3db","versionType":"git"},{"lessThan":"12b6d1a1715cbced2e445ca353f9c9987b8636e2","status":"affected","version":"06ed09351b67eb1114ae106a87a0ee3ea9adb3db","versionType":"git"},{"lessThan":"81241f734f0f662378f5ffc53882b012923e6fe5","status":"affected","version":"06ed09351b67eb1114ae106a87a0ee3ea9adb3db","versionType":"git"},{"lessThan":"8cc569696dac51fc62bb39b3b8f530582b916d29","status":"affected","version":"06ed09351b67eb1114ae106a87a0ee3ea9adb3db","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/btrfs/verity.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.6"},{"lessThan":"6.6","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.157","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.110","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.52","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.157","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.110","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.52","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.6","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"6.6","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: retry verity reads for not-uptodate Merkle folios\n\nbtrfs_read_merkle_tree_page() can find a folio in the mapping that is not\nuptodate.  After taking the folio lock, the current code treats that state\nas a read error and returns -EIO.\n\nThat can make a previous transient read failure sticky.  If the failed read\nleft a not-uptodate folio in the mapping, later callers find that folio and\nfail instead of retrying the read.\n\nKeep the existing page-cache insertion and locking order, but retry the\nMerkle item read when a not-uptodate folio is found in the mapping.  Also\nunlock the folio when read_key_bytes() fails so that a later caller can\nlock it and retry the read."}],"providerMetadata":{"dateUpdated":"2026-09-17T16:07:59.435Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/90e9eae1b5907fa36620ffb7f4f1a4afa9333427"},{"url":"https://git.kernel.org/stable/c/c1fa005cdf3b7ff14cdfd7d512830088a3fc256b"},{"url":"https://git.kernel.org/stable/c/12b6d1a1715cbced2e445ca353f9c9987b8636e2"},{"url":"https://git.kernel.org/stable/c/81241f734f0f662378f5ffc53882b012923e6fe5"},{"url":"https://git.kernel.org/stable/c/8cc569696dac51fc62bb39b3b8f530582b916d29"}],"title":"btrfs: retry verity reads for not-uptodate Merkle folios","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-90262","datePublished":"2026-09-17T16:07:59.435Z","dateReserved":"2026-09-11T19:38:34.796Z","dateUpdated":"2026-09-17T16:07:59.435Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-17 17:17:22","lastModifiedDate":"2026-09-17 17:17:22","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"90262","Ordinal":"1","Title":"btrfs: retry verity reads for not-uptodate Merkle folios","CVE":"CVE-2026-90262","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"90262","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: retry verity reads for not-uptodate Merkle folios\n\nbtrfs_read_merkle_tree_page() can find a folio in the mapping that is not\nuptodate.  After taking the folio lock, the current code treats that state\nas a read error and returns -EIO.\n\nThat can make a previous transient read failure sticky.  If the failed read\nleft a not-uptodate folio in the mapping, later callers find that folio and\nfail instead of retrying the read.\n\nKeep the existing page-cache insertion and locking order, but retry the\nMerkle item read when a not-uptodate folio is found in the mapping.  Also\nunlock the folio when read_key_bytes() fails so that a later caller can\nlock it and retry the read.","Type":"Description","Title":"btrfs: retry verity reads for not-uptodate Merkle folios"}]}}}