CVE-2026-53165

published 25 Jun 2026 · updated 5 Aug 2026

iomap: avoid potential null folio->mapping deref during error reporting

7.5HighCVSS 7.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1ad453817a4077230d1ba88eb0868f05f824449a and Kernel 2eea7f44b9c8b42fd7d3a1a87c06a7cd1b99c327.

In the Linux kernel, the following vulnerability has been resolved: iomap: avoid potential null folio->mapping deref during error reporting When a buffered read fails, iomap_finish_folio_read() reports the error with fserror_report_io(folio->mapping->host, ...). This is called after ifs->read_bytes_pending has been decremented by the bytes attempted to be read. For a folio split across multiple read completions, the folio is only guaranteed to stay locked while read_bytes_pending > 0. Once iomap_finish_folio_read() decrements read_bytes_pending, another in-flight read can complete and end the read on the folio, which unlocks it. This allows truncate logic to run and detach the folio (set folio->mapping to NULL). The error reporting path then can dereference a NULL folio->mapping. As reported by Sam Sun, this is the race that can occur: CPU0: failed completion CPU1: final completion CPU2: truncate ----------------------- ---------------------- -------------- read_bytes_pending -= len finished = false /* preempted before fserror_report_io() */ read_bytes_pending -= len finished = true folio_end_read() truncate clears folio->mapping fserror_report_io( folio->mapping->host, ...) ^ NULL deref Fix this by reporting the error first before decrementing ifs->read_bytes_pending.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=7.0, >=a9d573ee88af980f14fdadb5c12bbf6a195fb3f1 <1ad453817a4077230d1ba88eb0868f05f824449a, >=a9d573ee88af980f14fdadb5c12bbf6a195fb3f1 <2eea7f44b9c8b42fd7d3a1a87c06a7cd1b99c3271ad453817a4077230d1ba88eb0868f05f824449a, 2eea7f44b9c8b42fd7d3a1a87c06a7cd1b99c327

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-53165 severity on Zeptric[![CVE-2026-53165](https://zeptric.io/badge/cve/CVE-2026-53165.svg)](https://zeptric.io/cve/CVE-2026-53165)