CVE-2026-90360 — regulator: core: use system_freezable_wq for init complete work
In the Linux kernel, the following vulnerability has been resolved: regulator: core: use system_freezable_wq for init complete work schedule_delayed_work() uses system_wq, which is non-freezable, allowing regulator_init_complete_work to run concurrently with system suspend. This work fires ~30s after boot to disable unused regulators via I2C. When it races with PM suspend, the I2C adapter may already be suspended, triggering a -ESHUTDOWN warning in __i2c_transfer(): WARNING: ... at __i2c_transfer+0x36c/0x3c8 Call trace: __i2c_transfer i2c_transfer regmap_i2c_write _regmap_update_bits regulator_disable_regmap _regulator_do_disable regulator_late_cleanup regulator_init_complete_work_function process_one_work Switch to system_freezable_wq so the work is frozen before any device is suspended, eliminating the race.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 55576cf1853798e86f620766e23b604c9224c19c and < 03eab318cedd6ae34ecd34533cd986edf5237164version 5.4≥ 5.3.4 and < 5.4≥ 5.2.19 and < 5.3≥ 4.19.77 and < 4.20≥ 4.14.147 and < 4.14.160≥ 4.9.195 and < 4.9.207version 3fbfa415a5dd8fc78076c1ead160a03a058cd9f6 and 11 moreversion d6acb54716ffab29f15c66082bd751410b284764version c4f65c2fb0f5c488d4ae606fba94bb98dcf383fd≥ 8b8c8d69b1a31004517d4c71a490f47bdf3405a2 and < 8a2ae3ab348cce44120667277c2198f10cc348b1≥ 55576cf1853798e86f620766e23b604c9224c19c and < 29dc2e24f6adb36dcb884acf455644c397a67471≥ 55576cf1853798e86f620766e23b604c9224c19c and < 0b950aa7ec95e120b2bde745ca9a7ed3ce49d528≥ 55576cf1853798e86f620766e23b604c9224c19c and < 0d23d658d79925076026fff62a49b8c94e0e8922≥ 55576cf1853798e86f620766e23b604c9224c19c and < 6d0a2c5e210f2fba099129e6183ef81316a6ae48≥ 55576cf1853798e86f620766e23b604c9224c19c and < dc8570a5b830190bf0b57017c35aef97cd6ad7d9≥ 55576cf1853798e86f620766e23b604c9224c19c and < 9cf65270c1c1717c84dcfacd58a782c1186b0cbf≥ 55576cf1853798e86f620766e23b604c9224c19c and < 2cebc00340a585adeffe321bc41f1937eb79a4dc≥ d7ce17fba6c8e316ca9a554a87edddce6f862435 and < 350a0cba90e1bd40b1fe5b396923d2f3a61d1056 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.25%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
10 on the record
- git.kernel.org/stable/c/dc8570a5b830190bf0b57017c35aef97cd6ad7d9
- git.kernel.org/stable/c/0d23d658d79925076026fff62a49b8c94e0e8922
- git.kernel.org/stable/c/03eab318cedd6ae34ecd34533cd986edf5237164
- git.kernel.org/stable/c/0b950aa7ec95e120b2bde745ca9a7ed3ce49d528
- git.kernel.org/stable/c/29dc2e24f6adb36dcb884acf455644c397a67471
- git.kernel.org/stable/c/8a2ae3ab348cce44120667277c2198f10cc348b1
- git.kernel.org/stable/c/9cf65270c1c1717c84dcfacd58a782c1186b0cbf
- git.kernel.org/stable/c/6d0a2c5e210f2fba099129e6183ef81316a6ae48
- git.kernel.org/stable/c/2cebc00340a585adeffe321bc41f1937eb79a4dc
- git.kernel.org/stable/c/350a0cba90e1bd40b1fe5b396923d2f3a61d1056
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 6h
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 6h
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 6h
- Unknown CVE-2026-98861 fprobe: Use guard(rcu_sched_notrace) and check rcu_is_watching() 6h
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 6h
- Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 6h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-90360 is "regulator: core: use system_freezable_wq for init complete work", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.25% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.