{"api_version":"1","generated_at":"2026-07-24T23:00:11+00:00","cve":"CVE-2026-63820","urls":{"html":"https://cve.report/CVE-2026-63820","api":"https://cve.report/api/cve/CVE-2026-63820.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-63820","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-63820"},"summary":{"title":"f2fs: fix missing read bio submission on large folio error","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix missing read bio submission on large folio error\n\nf2fs_read_data_large_folio() can keep a read bio across multiple\nreadahead folios.  If a later folio hits an error before any of its\nblocks are added to the bio, folio_in_bio is false and the current error\npath returns immediately after ending that folio.\n\nThis can leave the bio accumulated for earlier folios unsubmitted.  Those\nfolios then never receive read completion, and readers can wait\nindefinitely on the locked folios.\n\nRoute errors through the common out path so any pending bio is submitted\nbefore returning.  Stop consuming more readahead folios once an error is\nseen, and only wait on and clear the current folio when it was actually\nadded to the bio.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-07-19 12:16:55","updated_at":"2026-07-19 12:16:55"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/48c92559e7b66fdc3cbc74f6e152e66ec0150a0a","name":"https://git.kernel.org/stable/c/48c92559e7b66fdc3cbc74f6e152e66ec0150a0a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/74c8d2ec95c59a5651ecd975c466998af1961fd4","name":"https://git.kernel.org/stable/c/74c8d2ec95c59a5651ecd975c466998af1961fd4","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-63820","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63820","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected a5d8b9d94e1863f3ebb7182c238b2c713f6f4efd 48c92559e7b66fdc3cbc74f6e152e66ec0150a0a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected a5d8b9d94e1863f3ebb7182c238b2c713f6f4efd 74c8d2ec95c59a5651ecd975c466998af1961fd4 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.0","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.3 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"63820","cve":"CVE-2026-63820","epss":"0.001450000","percentile":"0.041950000","score_date":"2026-07-20","updated_at":"2026-07-21 00:13:14"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/f2fs/data.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"48c92559e7b66fdc3cbc74f6e152e66ec0150a0a","status":"affected","version":"a5d8b9d94e1863f3ebb7182c238b2c713f6f4efd","versionType":"git"},{"lessThan":"74c8d2ec95c59a5651ecd975c466998af1961fd4","status":"affected","version":"a5d8b9d94e1863f3ebb7182c238b2c713f6f4efd","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/f2fs/data.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"7.0"},{"lessThan":"7.0","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.3","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.3","versionStartIncluding":"7.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc1","versionStartIncluding":"7.0","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix missing read bio submission on large folio error\n\nf2fs_read_data_large_folio() can keep a read bio across multiple\nreadahead folios.  If a later folio hits an error before any of its\nblocks are added to the bio, folio_in_bio is false and the current error\npath returns immediately after ending that folio.\n\nThis can leave the bio accumulated for earlier folios unsubmitted.  Those\nfolios then never receive read completion, and readers can wait\nindefinitely on the locked folios.\n\nRoute errors through the common out path so any pending bio is submitted\nbefore returning.  Stop consuming more readahead folios once an error is\nseen, and only wait on and clear the current folio when it was actually\nadded to the bio."}],"providerMetadata":{"dateUpdated":"2026-07-19T12:02:18.211Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/48c92559e7b66fdc3cbc74f6e152e66ec0150a0a"},{"url":"https://git.kernel.org/stable/c/74c8d2ec95c59a5651ecd975c466998af1961fd4"}],"title":"f2fs: fix missing read bio submission on large folio error","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-63820","datePublished":"2026-07-19T12:02:18.211Z","dateReserved":"2026-07-19T07:54:57.014Z","dateUpdated":"2026-07-19T12:02:18.211Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-07-19 12:16:55","lastModifiedDate":"2026-07-19 12:16:55","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"63820","Ordinal":"1","Title":"f2fs: fix missing read bio submission on large folio error","CVE":"CVE-2026-63820","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"63820","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix missing read bio submission on large folio error\n\nf2fs_read_data_large_folio() can keep a read bio across multiple\nreadahead folios.  If a later folio hits an error before any of its\nblocks are added to the bio, folio_in_bio is false and the current error\npath returns immediately after ending that folio.\n\nThis can leave the bio accumulated for earlier folios unsubmitted.  Those\nfolios then never receive read completion, and readers can wait\nindefinitely on the locked folios.\n\nRoute errors through the common out path so any pending bio is submitted\nbefore returning.  Stop consuming more readahead folios once an error is\nseen, and only wait on and clear the current folio when it was actually\nadded to the bio.","Type":"Description","Title":"f2fs: fix missing read bio submission on large folio error"}]}}}