CVE-2026-90360: regulator: core: use system_freezable_wq for init complete work
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.24% (FIRST EPSS).
- Fixed version: Linux Linux 03eab318cedd6ae34ecd34533cd986edf5237164, 0b950aa7ec95e120b2bde745ca9a7ed3ce49d528, 0d23d658d79925076026fff62a49b8c94e0e8922.
Low priority for now. Upgrade to Linux Linux 03eab318cedd6ae34ecd34533cd986edf5237164, 0b950aa7ec95e120b2bde745ca9a7ed3ce49d528, 0d23d658d79925076026fff62a49b8c94e0e8922 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: 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.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 15th 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
- c4f65c2fb0f5c488d4ae606fba94bb98dcf383fd, d6acb54716ffab29f15c66082bd751410b284764, 3fbfa415a5dd8fc78076c1ead160a03a058cd9f6, 5.4affected
- 8b8c8d69b1a31004517d4c71a490f47bdf3405a2 and later · before 8a2ae3ab348cce44120667277c2198f10cc348b1affected · git
- d7ce17fba6c8e316ca9a554a87edddce6f862435 and later · before 350a0cba90e1bd40b1fe5b396923d2f3a61d1056affected · git
- 55576cf1853798e86f620766e23b604c9224c19c and later · before 2cebc00340a585adeffe321bc41f1937eb79a4dcaffected · git
- 55576cf1853798e86f620766e23b604c9224c19c and later · before 9cf65270c1c1717c84dcfacd58a782c1186b0cbfaffected · git
- 55576cf1853798e86f620766e23b604c9224c19c and later · before dc8570a5b830190bf0b57017c35aef97cd6ad7d9affected · git
- 55576cf1853798e86f620766e23b604c9224c19c and later · before 6d0a2c5e210f2fba099129e6183ef81316a6ae48affected · git
- 55576cf1853798e86f620766e23b604c9224c19c and later · before 0d23d658d79925076026fff62a49b8c94e0e8922affected · git
- 55576cf1853798e86f620766e23b604c9224c19c and later · before 0b950aa7ec95e120b2bde745ca9a7ed3ce49d528affected · git
- 55576cf1853798e86f620766e23b604c9224c19c and later · before 29dc2e24f6adb36dcb884acf455644c397a67471affected · git
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 | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-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-90358Sep 17, 2026 · bpf, x86: Fix trampoline stack size for 128-bit arguments31Monitor
- ← EarlierCVE-2026-90359Sep 17, 2026 · bpf: Reject >8 byte return values on return-reading trampoline paths0Monitor
- Later →CVE-2026-90361Sep 17, 2026 · wifi: ath11k: fix leak in ath11k_service_ready_ext_event()0Monitor
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 | 03eab318cedd6ae34ecd34533cd986edf5237164 | Vendor (CNA) |
| Linux Linux | 0b950aa7ec95e120b2bde745ca9a7ed3ce49d528 | Vendor (CNA) |
| Linux Linux | 0d23d658d79925076026fff62a49b8c94e0e8922 | Vendor (CNA) |
| Linux Linux | 29dc2e24f6adb36dcb884acf455644c397a67471 | Vendor (CNA) |
| Linux Linux | 2cebc00340a585adeffe321bc41f1937eb79a4dc | Vendor (CNA) |
| Linux Linux | 350a0cba90e1bd40b1fe5b396923d2f3a61d1056 | Vendor (CNA) |
| Linux Linux | 4.14.160 | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 4.9.207 | Vendor (CNA) |
| Linux Linux | 5.3 | Vendor (CNA) |
| Linux Linux | 5.4 | Vendor (CNA) |
| Linux Linux | 6d0a2c5e210f2fba099129e6183ef81316a6ae48 | Vendor (CNA) |
| Linux Linux | 8a2ae3ab348cce44120667277c2198f10cc348b1 | Vendor (CNA) |
| Linux Linux | 9cf65270c1c1717c84dcfacd58a782c1186b0cbf | Vendor (CNA) |
| Linux Linux | dc8570a5b830190bf0b57017c35aef97cd6ad7d9 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | 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 (9 more)Show less
- git.kernel.org/stable/c/0b950aa7ec95e120b2bde745ca9a7ed3ce49d528
- git.kernel.org/stable/c/0d23d658d79925076026fff62a49b8c94e0e8922
- git.kernel.org/stable/c/29dc2e24f6adb36dcb884acf455644c397a67471
- git.kernel.org/stable/c/2cebc00340a585adeffe321bc41f1937eb79a4dc
- git.kernel.org/stable/c/350a0cba90e1bd40b1fe5b396923d2f3a61d1056
- git.kernel.org/stable/c/6d0a2c5e210f2fba099129e6183ef81316a6ae48
- git.kernel.org/stable/c/8a2ae3ab348cce44120667277c2198f10cc348b1
- git.kernel.org/stable/c/9cf65270c1c1717c84dcfacd58a782c1186b0cbf
- git.kernel.org/stable/c/dc8570a5b830190bf0b57017c35aef97cd6ad7d9
Vendor advisories and official records. Exploit/PoC links are deliberately left out.