CVE-2026-90182blk-iocost: clear delay state when freeing policy data
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 43 days later
· 43 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < 6942cb740fb17b24731728b25994eba361776011
- affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < 6b59f976db5def818829fc1eb4efc0a5c8c2f0cf
- affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < 8b4d0b1b3079bbe9a5366e2c8020eb22926733b6
- affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < b399a88eb8b16c5a1a3645fd49ff507fb82b363c
- affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < b9c16db833e3ff15d923282f94dddf0e10fab8c0
- affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < 97cb95d2148835ae86ff916b145aef332d40439d
- affected 5.4
- unaffected < 5.4
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/6942cb740fb17b24731728b25994eba361776011 (opens in a new tab)
- https://git.kernel.org/stable/c/6b59f976db5def818829fc1eb4efc0a5c8c2f0cf (opens in a new tab)
- https://git.kernel.org/stable/c/8b4d0b1b3079bbe9a5366e2c8020eb22926733b6 (opens in a new tab)
- https://git.kernel.org/stable/c/b399a88eb8b16c5a1a3645fd49ff507fb82b363c (opens in a new tab)
- https://git.kernel.org/stable/c/b9c16db833e3ff15d923282f94dddf0e10fab8c0 (opens in a new tab)
- https://git.kernel.org/stable/c/97cb95d2148835ae86ff916b145aef332d40439d (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-81775 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90182)Record last updated .