{"api_version":"1","generated_at":"2026-06-26T11:05:07+00:00","cve":"CVE-2026-53165","urls":{"html":"https://cve.report/CVE-2026-53165","api":"https://cve.report/api/cve/CVE-2026-53165.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-53165","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-53165"},"summary":{"title":"iomap: avoid potential null folio->mapping deref during error reporting","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niomap: avoid potential null folio->mapping deref during error reporting\n\nWhen a buffered read fails, iomap_finish_folio_read() reports the error\nwith fserror_report_io(folio->mapping->host, ...). This is called after\nifs->read_bytes_pending has been decremented by the bytes attempted to\nbe read.\n\nFor a folio split across multiple read completions, the folio is only\nguaranteed to stay locked while read_bytes_pending > 0. Once\niomap_finish_folio_read() decrements read_bytes_pending, another\nin-flight read can complete and end the read on the folio, which unlocks\nit. This allows truncate logic to run and detach the folio (set\nfolio->mapping to NULL). The error reporting path then can dereference a\nNULL folio->mapping. As reported by Sam Sun, this is the race that can\noccur:\n\nCPU0: failed completion      CPU1: final completion     CPU2: truncate\n-----------------------      ----------------------     --------------\nread_bytes_pending -= len\nfinished = false\n/* preempted before\n   fserror_report_io() */\n\t\t\t     read_bytes_pending -= len\n\t\t\t     finished = true\n\t\t\t     folio_end_read()\n\t\t\t\t\t\t\ttruncate clears\n\t\t\t\t\t\t\tfolio->mapping\nfserror_report_io(\n  folio->mapping->host, ...)\n\t      ^ NULL deref\n\nFix this by reporting the error first before decrementing\nifs->read_bytes_pending.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-06-25 09:16:33","updated_at":"2026-06-25 09:16:33"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/1ad453817a4077230d1ba88eb0868f05f824449a","name":"https://git.kernel.org/stable/c/1ad453817a4077230d1ba88eb0868f05f824449a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/2eea7f44b9c8b42fd7d3a1a87c06a7cd1b99c327","name":"https://git.kernel.org/stable/c/2eea7f44b9c8b42fd7d3a1a87c06a7cd1b99c327","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53165","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53165","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected a9d573ee88af980f14fdadb5c12bbf6a195fb3f1 1ad453817a4077230d1ba88eb0868f05f824449a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected a9d573ee88af980f14fdadb5c12bbf6a195fb3f1 2eea7f44b9c8b42fd7d3a1a87c06a7cd1b99c327 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.0.13 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"53165","cve":"CVE-2026-53165","epss":"0.001800000","percentile":"0.077730000","score_date":"2026-06-25","updated_at":"2026-06-26 00:06:14"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/iomap/buffered-io.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"1ad453817a4077230d1ba88eb0868f05f824449a","status":"affected","version":"a9d573ee88af980f14fdadb5c12bbf6a195fb3f1","versionType":"git"},{"lessThan":"2eea7f44b9c8b42fd7d3a1a87c06a7cd1b99c327","status":"affected","version":"a9d573ee88af980f14fdadb5c12bbf6a195fb3f1","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/iomap/buffered-io.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.0.*","status":"unaffected","version":"7.0.13","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.13","versionStartIncluding":"7.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1","versionStartIncluding":"7.0","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\niomap: avoid potential null folio->mapping deref during error reporting\n\nWhen a buffered read fails, iomap_finish_folio_read() reports the error\nwith fserror_report_io(folio->mapping->host, ...). This is called after\nifs->read_bytes_pending has been decremented by the bytes attempted to\nbe read.\n\nFor a folio split across multiple read completions, the folio is only\nguaranteed to stay locked while read_bytes_pending > 0. Once\niomap_finish_folio_read() decrements read_bytes_pending, another\nin-flight read can complete and end the read on the folio, which unlocks\nit. This allows truncate logic to run and detach the folio (set\nfolio->mapping to NULL). The error reporting path then can dereference a\nNULL folio->mapping. As reported by Sam Sun, this is the race that can\noccur:\n\nCPU0: failed completion      CPU1: final completion     CPU2: truncate\n-----------------------      ----------------------     --------------\nread_bytes_pending -= len\nfinished = false\n/* preempted before\n   fserror_report_io() */\n\t\t\t     read_bytes_pending -= len\n\t\t\t     finished = true\n\t\t\t     folio_end_read()\n\t\t\t\t\t\t\ttruncate clears\n\t\t\t\t\t\t\tfolio->mapping\nfserror_report_io(\n  folio->mapping->host, ...)\n\t      ^ NULL deref\n\nFix this by reporting the error first before decrementing\nifs->read_bytes_pending."}],"providerMetadata":{"dateUpdated":"2026-06-25T08:38:45.445Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/1ad453817a4077230d1ba88eb0868f05f824449a"},{"url":"https://git.kernel.org/stable/c/2eea7f44b9c8b42fd7d3a1a87c06a7cd1b99c327"}],"title":"iomap: avoid potential null folio->mapping deref during error reporting","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-53165","datePublished":"2026-06-25T08:38:45.445Z","dateReserved":"2026-06-09T07:44:35.389Z","dateUpdated":"2026-06-25T08:38:45.445Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-25 09:16:33","lastModifiedDate":"2026-06-25 09:16:33","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"53165","Ordinal":"1","Title":"iomap: avoid potential null folio->mapping deref during error re","CVE":"CVE-2026-53165","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"53165","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\niomap: avoid potential null folio->mapping deref during error reporting\n\nWhen a buffered read fails, iomap_finish_folio_read() reports the error\nwith fserror_report_io(folio->mapping->host, ...). This is called after\nifs->read_bytes_pending has been decremented by the bytes attempted to\nbe read.\n\nFor a folio split across multiple read completions, the folio is only\nguaranteed to stay locked while read_bytes_pending > 0. Once\niomap_finish_folio_read() decrements read_bytes_pending, another\nin-flight read can complete and end the read on the folio, which unlocks\nit. This allows truncate logic to run and detach the folio (set\nfolio->mapping to NULL). The error reporting path then can dereference a\nNULL folio->mapping. As reported by Sam Sun, this is the race that can\noccur:\n\nCPU0: failed completion      CPU1: final completion     CPU2: truncate\n-----------------------      ----------------------     --------------\nread_bytes_pending -= len\nfinished = false\n/* preempted before\n   fserror_report_io() */\n\t\t\t     read_bytes_pending -= len\n\t\t\t     finished = true\n\t\t\t     folio_end_read()\n\t\t\t\t\t\t\ttruncate clears\n\t\t\t\t\t\t\tfolio->mapping\nfserror_report_io(\n  folio->mapping->host, ...)\n\t      ^ NULL deref\n\nFix this by reporting the error first before decrementing\nifs->read_bytes_pending.","Type":"Description","Title":"iomap: avoid potential null folio->mapping deref during error re"}]}}}