CVE-2026-90183 Affecting ocfs2-kmp-default package, versions <6.4.0-150700.53.84.1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-SLES157-OCFS2KMPDEFAULT-21170849
- published17 Oct 2026
- disclosed16 Oct 2026
Introduced: 16 Oct 2026
NewCVE-2026-90183 (opens in a new tab)How to fix?
Upgrade SLES:15.7 ocfs2-kmp-default to version 6.4.0-150700.53.84.1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream ocfs2-kmp-default package and not the ocfs2-kmp-default package as distributed by SLES.
See How to fix? for SLES:15.7 relevant fixed versions and status.
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.
References
- https://www.suse.com/security/cve/CVE-2026-90183.html
- https://bugzilla.suse.com/1281964
- https://git.kernel.org/stable/c/02f1b90ab33ef99c89dd96a385b432ff57abc64d
- https://git.kernel.org/stable/c/8935bf22c0a0db517a7f72f7097300e05dd852f5
- https://git.kernel.org/stable/c/5c6593422eb3c3a21505436ccf74599a433584c8