CVE-2026-90360

regulator: core: use system_freezable_wq for init complete work

N/A
Published: September 17, 2026 at 04:09 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3fbfa415a5dd8fc78076c1ead160a03a058cd9f64.14.1474.19.774.9.1955.2.195.3.45.455576cf1853798e86f620766e23b604c9224c19c8b8c8d69b1a31004517d4c71a490f47bdf3405a2c4f65c2fb0f5c488d4ae606fba94bb98dcf383fdd6acb54716ffab29f15c66082bd751410b284764d7ce17fba6c8e316ca9a554a87edddce6f862435
Vendor states this is fixed in 03eab318cedd6ae34ecd34533cd986edf5237164 (fixed)
Vendor states this is fixed in 0b950aa7ec95e120b2bde745ca9a7ed3ce49d528 (fixed)
Vendor states this is fixed in 0d23d658d79925076026fff62a49b8c94e0e8922 (fixed)
Vendor states this is fixed in 29dc2e24f6adb36dcb884acf455644c397a67471 (fixed)
Vendor states this is fixed in 2cebc00340a585adeffe321bc41f1937eb79a4dc (fixed)
Vendor states this is fixed in 350a0cba90e1bd40b1fe5b396923d2f3a61d1056 (fixed)
Vendor states this is fixed in 6d0a2c5e210f2fba099129e6183ef81316a6ae48 (fixed)
Vendor states this is fixed in 8a2ae3ab348cce44120667277c2198f10cc348b1 (fixed)
Vendor states this is fixed in 9cf65270c1c1717c84dcfacd58a782c1186b0cbf (fixed)
Vendor states this is fixed in dc8570a5b830190bf0b57017c35aef97cd6ad7d9 (fixed)
Vendor states this is fixed in 4.14.160 (unaffected)
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.9.207 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Affected range stops below 5.3, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.4 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card