# CVE-2026-90360: regulator: core: use system_freezable_wq for init complete work

> A race condition in the Linux kernel regulator core allows work to run during suspend, causing I2C errors and potential system instability or denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102236, BELL-CVE-2026-90360, DEBIAN-CVE-2026-90360, GHSA-8q97-2m9m-f966, UBUNTU-CVE-2026-90360

## What is CVE-2026-90360?

CVE-2026-90360 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-90360?


## How do I fix CVE-2026-90360?

Apply the vendor's patch.

## Is CVE-2026-90360 being exploited?

There is no known exploitation of CVE-2026-90360 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90360 and fix it if it is affected.

What it is: CVE-2026-90360 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90360 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90360/ (Markdown: https://insights.sbomify.com/CVE-2026-90360/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90360
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90360
- OSV: https://osv.dev/vulnerability/CVE-2026-90360

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90360/
Summaries are generated and may contain mistakes; the official description above is the record.