{
  "affected": [
    {
      "ranges": [
        {
          "events": [
            {
              "introduced": "7caa47151ab2e644dd221f741ec7578d9532c9a3"
            },
            {
              "fixed": "b9c16db833e3ff15d923282f94dddf0e10fab8c0"
            },
            {
              "fixed": "97cb95d2148835ae86ff916b145aef332d40439d"
            }
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "type": "GIT"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Linux",
        "name": "Kernel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "5.4.0"
            },
            {
              "fixed": "7.2.6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90182.json"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nblk-iocost: clear delay state when freeing policy data\n\niocg_kick_delay() turns sufficiently large debt into an explicit\nblock-cgroup delay with blkcg_set_delay(), setting blkg-\u003euse_delay to\n-1 and incrementing blkcg-\u003econgestion_count.  Clearing it again depends\non iocg_kick_delay() running from the period timer, the waitq timer or\nthe issue path.\n\nioc_pd_free() removes the iocg from active_iocgs and cancels its waitq\ntimer, and no further bios can arrive, so once it has run nothing is\nleft which can reduce the debt and clear the delay.  The blkcg stays\nmarked congested for the rest of its life.\n\nblk_cgroup_congested() then returns true for every task in that cgroup\nand its descendants: page_cache_sync_ra() cuts readahead to a single\npage, page_cache_async_ra() skips it altogether, and\n__folio_throttle_swaprate() takes swap_avail_lock and schedules a\nthrottle on anonymous folio allocation.\n\nClear it explicitly, after the list removal and the synchronous\nhrtimer_cancel() so that neither timer processing nor an I/O path can\nre-arm it.  The free callback can also see policy data which was never\nattached to a blkg, hence the pd-\u003eblkg check.",
  "id": "CVE-2026-90182",
  "modified": "2026-09-19T03:30:41.744578434Z",
  "published": "2026-09-17T16:07:06.388Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/97cb95d2148835ae86ff916b145aef332d40439d"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b9c16db833e3ff15d923282f94dddf0e10fab8c0"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90182.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90182"
    },
    {
      "type": "PACKAGE",
      "url": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
    }
  ],
  "schema_version": "1.9.0",
  "summary": "blk-iocost: clear delay state when freeing policy data"
}