CVE-2026-90183

published 17 Sep 2026 · updated 15 Nov 2026

blk-iolatency: clear delay state when freeing policy data

5.0MediumEPSS 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 b6449a915d1826e1450f6368fc379fe44caa06ca, Kernel 02f1b90ab33ef99c89dd96a385b432ff57abc64d, Kernel 27573278b1cbc2313ebd31309ac18ac6179b828a and 8 more.

In the Linux kernel, the following vulnerability has been resolved: blk-iolatency: clear delay state when freeing policy data io.latency can throttle a group which has no latency target of its own. When a sibling misses its target, check_scale_change() scales down its peers, and a peer that reaches queue depth one gets blkcg_use_delay() called on it on every further scale-down, even with min_lat_nsec == 0. iolatency_pd_offline() resets the target through iolatency_set_min_lat_nsec(), which clears the delay only on a nonzero to zero transition, so it never clears such a peer. Freeing the policy data then leaves blkg->use_delay set and blkcg->congestion_count elevated with nothing left that can drop it. blk_cgroup_congested() then returns true for every task in that cgroup and its descendants for as long as the cgroup lives: 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 the delay in iolatency_pd_free(). By then bio-held blkg references have drained, or the queue is frozen for policy deactivation, so check_scale_change() cannot re-arm it. The free callback can also see policy data which was never attached to a blkg, hence the pd->blkg check.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=d70675121546c35feaceebf7ed9caed8716640f3 <b6449a915d1826e1450f6368fc379fe44caa06ca, >=d70675121546c35feaceebf7ed9caed8716640f3 <02f1b90ab33ef99c89dd96a385b432ff57abc64d, >=d70675121546c35feaceebf7ed9caed8716640f3 <27573278b1cbc2313ebd31309ac18ac6179b828a, >=d70675121546c35feaceebf7ed9caed8716640f3 <53ccb4b967edc5f82ff6f9c066fb96c31aa7561a, >=d70675121546c35feaceebf7ed9caed8716640f3 <5c6593422eb3c3a21505436ccf74599a433584c8, >=d70675121546c35feaceebf7ed9caed8716640f3 <8935bf22c0a0db517a7f72f7097300e05dd852f5, =4.19b6449a915d1826e1450f6368fc379fe44caa06ca, 02f1b90ab33ef99c89dd96a385b432ff57abc64d, 27573278b1cbc2313ebd31309ac18ac6179b828a, 53ccb4b967edc5f82ff6f9c066fb96c31aa7561a, 5c6593422eb3c3a21505436ccf74599a433584c8, 8935bf22c0a0db517a7f72f7097300e05dd852f5
linux-kernel: Kernel>=6.13.0 <6.18.57, >=6.19.0 <7.2.6, >=6.2.0 <6.6.160, >=6.7.0 <6.12.114, >=4.19.0 <6.1.1916.18.57, 7.2.6, 6.6.160, 6.12.114, 6.1.191

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-90183 severity on Zeptric[![CVE-2026-90183](https://zeptric.io/badge/cve/CVE-2026-90183.svg)](https://zeptric.io/cve/CVE-2026-90183)