CVE-2026-90183: blk-iolatency: clear delay state when freeing policy data
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 02f1b90ab33ef99c89dd96a385b432ff57abc64d, 53ccb4b967edc5f82ff6f9c066fb96c31aa7561a, 5c6593422eb3c3a21505436ccf74599a433584c8.
Low priority for now. Upgrade to Linux Linux 02f1b90ab33ef99c89dd96a385b432ff57abc64d, 53ccb4b967edc5f82ff6f9c066fb96c31aa7561a, 5c6593422eb3c3a21505436ccf74599a433584c8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 21, 2026
- EPSS
- 0.2% · 9th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.19affected
- d70675121546c35feaceebf7ed9caed8716640f3 and later · before 53ccb4b967edc5f82ff6f9c066fb96c31aa7561aaffected · git
- d70675121546c35feaceebf7ed9caed8716640f3 and later · before b6449a915d1826e1450f6368fc379fe44caa06caaffected · git
- d70675121546c35feaceebf7ed9caed8716640f3 and later · before 5c6593422eb3c3a21505436ccf74599a433584c8affected · git
- d70675121546c35feaceebf7ed9caed8716640f3 and later · before 02f1b90ab33ef99c89dd96a385b432ff57abc64daffected · git
- d70675121546c35feaceebf7ed9caed8716640f3 and later · before 8935bf22c0a0db517a7f72f7097300e05dd852f5affected · git
- before 4.19not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.114 and later · up to and including 6.12.*not affected · semver
- 6.18.57 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.2.8-1.1 | 7.2.8-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90181Sep 17, 2026 · ublk: avoid teardown retry loop on xarray allocation failure0Monitor
- ← EarlierCVE-2026-90182Sep 17, 2026 · blk-iocost: clear delay state when freeing policy data0Monitor
- Later →CVE-2026-90184Sep 17, 2026 · null_blk: serialize configfs attribute updates with device setup0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 02f1b90ab33ef99c89dd96a385b432ff57abc64d | Vendor (CNA) |
| Linux Linux | 53ccb4b967edc5f82ff6f9c066fb96c31aa7561a | Vendor (CNA) |
| Linux Linux | 5c6593422eb3c3a21505436ccf74599a433584c8 | Vendor (CNA) |
| Linux Linux | 8935bf22c0a0db517a7f72f7097300e05dd852f5 | Vendor (CNA) |
| Linux Linux | b6449a915d1826e1450f6368fc379fe44caa06ca | Vendor (CNA) |
| debian:linux | 7.2.6-1 · Debian:14 | Package registry (OSV) |
| opensuse:kernel-source | 7.2.8-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.