CVE-2026-90183

Persistent workload throttling via uncleared cgroup delay state

Published Sep 17, 2026 · Updated Sep 17, 2026

Denial of service in Linux 4.19 blk-iolatency allows local users to persistently throttle cgroup workloads via stale delay state. In block/blk-iolatency.c, iolatency_pd_offline() clears delay only when a nonzero latency target becomes zero, leaving delay and congestion accounting set for throttled peers that never had a target. The condition requires sibling latency pressure followed by policy-data teardown; affected cgroups and descendants retain reduced readahead and anonymous-memory allocation throttling for the cgroup's lifetime, without a reported crash.

CVSS severity2.0
Low
EPSS probability0.21%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Denial of service in Linux 4.19 blk-iolatency allows local users to persistently throttle cgroup workloads via stale delay state. In block/blk-iolatency.c, iolatency_pd_offline() clears delay only when a nonzero latency target becomes zero, leaving delay and congestion accounting set for throttled peers that never had a target. The condition requires sibling latency pressure followed by policy-data teardown; affected cgroups and descendants retain reduced readahead and anonymous-memory allocation throttling for the cgroup's lifetime, without a reported crash.

The record

CVE
CVE-2026-90183
Published
Sep 17, 2026
Updated
Sep 17, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 17, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.19
  2. Affected versionversion=d70675121546c35feaceebf7ed9caed8716640f3 <02f1b90ab33ef99c89dd96a385b432ff57abc64d
  3. Affected versionversion=d70675121546c35feaceebf7ed9caed8716640f3 <8935bf22c0a0db517a7f72f7097300e05dd852f5

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=4.19; version=d70675121546c35feaceebf7ed9caed8716640f3 <02f1b90ab33ef99c89dd96a385b432ff57abc64d; version=d70675121546c35feaceebf7ed9caed8716640f3 <8935bf22c0a0db517a7f72f7097300e05dd852f5

Published CVSS scores

2.5SUSECVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
2.0SUSECVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
2.5Amazon LinuxCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started