{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.0.13-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  iomap: avoid potential null folio-\u003emapping deref during error reporting  When a buffered read fails, iomap_finish_folio_read() reports the error with fserror_report_io(folio-\u003emapping-\u003ehost, ...). This is called after ifs-\u003eread_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 \u003e 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-\u003emapping to NULL). The error reporting path then can dereference a NULL folio-\u003emapping. 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() */ \t\t\t     read_bytes_pending -= len \t\t\t     finished = true \t\t\t     folio_end_read() \t\t\t\t\t\t\ttruncate clears \t\t\t\t\t\t\tfolio-\u003emapping fserror_report_io(   folio-\u003emapping-\u003ehost, ...) \t      ^ NULL deref  Fix this by reporting the error first before decrementing ifs-\u003eread_bytes_pending.",
  "id": "DEBIAN-CVE-2026-53165",
  "modified": "2026-09-14T16:47:31.468536889Z",
  "published": "2026-06-25T09:16:33.893Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-53165"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-53165"
  ]
}