[CVE-2026-90360][LOW] Revert "regulator: Defer init completion for a while after late_initcall" This reverts commit 8b8c8d6 which is

[CVE-2026-90360][LOW] Revert "regulator: Defer init completion for a while after late_initcall" This reverts commit 8b8c8d6 which is

[AL-KERNEL]

CVE: CVE-2026-90360
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: Revert "regulator: Defer init completion for a while after late_initcall" This reverts commit 8b8c8d6 which is
Commit: 8a2ae3ab348cce44120667277c2198f10cc348b1
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8a2ae3ab348cce44120667277c2198f10cc348b1
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-90360
Analysis date: Thu, 17 Sep 2026 22:15:19 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-90360 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-90360

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-90360	LOW	https://www.kernelcve.org/list/?q=CVE-2026-90360 CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-362;CWE-667;CWE-703;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'The regulator init complete delayed work was queued on the non freezable system workqueue, so it could run while the system was entering suspend. During that race the late regulator cleanup path may try to disable unused regulators over I2C after the I2C adapter is already suspended, producing an ESHUTDOWN warning in __i2c_transfer and potentially disrupting suspend or platform power management. For the CVSS the PR:L is used because triggering normally requires a local user or local process that can request suspend at the relevant time after boot. The issue is not network reachable and there is no evidence of memory corruption, information disclosure, or privilege escalation from the patch context. Impact is primarily local denial of service or suspend reliability degradation, with availability impact depending on the affected hardware and power management policy.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1)	YES	INIT WARNONLY SIMPLEFIX RACE HARDWARE BOOT 	YES	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=1
PrimitiveClass=NONE
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 1
* Conservative score: 1
* Raw paranoid score: 1
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate**::

No floor or cap changed the score.

2. Signal breakdown

Positive signals:

* +1: Availability or suspend reliability degradation is plausible. The delayed regulator cleanup can run during suspend and issue I2C transfers after the adapter is suspended, producing an ESHUTDOWN warning and potentially disrupting the suspend path or platform power management.

Negative signals:

* No negative points applied. Although the bug is a race around suspend timing, the score is already very low and no extra penalty is needed.

Not awarded:

* Real UAF not awarded. The patch does not establish use after free, stale lifetime use, double release, or refcount corruption.
* CLASS_A or CLASS_B primitive not awarded. There is no controlled corruption, ownership violation, authorization bypass, semantic reinterpretation, or lifetime primitive.
* Reliable kernel crash not awarded. The supplied evidence shows a WARNING in __i2c_transfer, not a panic or host-wide fatal crash.
* Extra availability not awarded. Any availability concern is the same suspend or power-management disruption already counted.
* Confidentiality and integrity not awarded. No disclosure path, unauthorized write, or privilege escalation primitive is supported.
* Remote reachability not awarded. This is not packet-triggered or network reachable.
* Local unprivileged trigger not awarded. Some systems allow a local user to request suspend, but the supplied evidence does not prove below-host-admin reachability for the complete trigger path across deployments.
* Manual-review preservation not awarded. There is no unresolved memory corruption or security-boundary primitive.

3. Reachability analysis

The vulnerable sequence requires the delayed regulator_init_complete_work to run around the time the system enters suspend, roughly after the boot-time delay. The trigger depends on a local suspend operation and on hardware or board configuration where unused regulators are disabled through an I2C-backed regmap.

Host-admin-equivalent privilege is not positively established because suspend may be exposed to local users through desktop or service policy on some systems. Below-host-admin reachability is also not fully established from the patch alone because direct kernel suspend control is often policy or privilege gated. Therefore HostAdminRequired is UNKNOWN.

NamespaceScopedPrivilege is NO because this is a system-wide power-management path, not a namespace-scoped operation. No prior attacker-controlled namespace setup is relevant. No network trigger is established. No special rare hardware penalty is applied, but the practical effect depends on affected regulator and I2C platform topology.

Race repeatability is limited by the boot-time delayed work and suspend timing, but the demonstrated consequence is only a warning or suspend reliability issue.

4. Primitive and severity interpretation

The exact issue is a synchronization bug between non-freezable delayed work and the PM suspend sequence. The workqueue item may attempt regulator cleanup via I2C after the I2C adapter has already been suspended.

This is not active structured UAF and not fixed stale storage. It is a race-driven invalid-state power-management ordering issue. There is no concrete repeated release or refcount operation. There is no evidence that the first operation can free or destroy an object that is later mutated through the same dangling reference.

PrimitiveClass is NONE because no meaningful corruption, lifetime, ownership, authorization, or security-boundary primitive is established. The demonstrated consequence is an I2C warning and possible suspend disruption. The speculative consequence is broader suspend failure on affected platforms, but not memory corruption or privilege escalation.

ImportantCandidate is NO because the issue lacks a concrete exploitation primitive beyond local availability or suspend reliability degradation. AutoDowngradeAllowed is YES because automatic triage closure is reasonable when the product does not treat suspend reliability as a critical security availability requirement.

Likely operational severity is low. It is a stability and PM ordering fix rather than an Important-class kernel security issue.

5. One-sentence report phrase

The regulator init complete work could run on a non freezable workqueue during system suspend and attempt I2C regulator cleanup after the I2C adapter was suspended, causing an ESHUTDOWN warning and possible local suspend reliability DoS.

6. Manual review recommendation

NO MANUAL CHECK NEEDED

Reason: no UAF, no memory corruption, no authorization bypass, no network reachability, and no demonstrated kernel crash or privilege escalation primitive are established.

7. Call-site confidence

Call-site confidence: high

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: Revert "regulator: Defer init completion for a while after late_initcall" This reverts commit 8b8c8d6 which is
Commit: 8a2ae3ab348cce44120667277c2198f10cc348b1
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8a2ae3ab348cce44120667277c2198f10cc348b1

Commit description:

It's causing "odd" interactions with older kernels, so it probably isn't
a good idea to cause timing changes there.  This has been reported to
cause oopses on Pixel devices.

Reported-by: Siddharth Kapoor <ksiddharth@google.com>
Cc: Mark Brown <broonie@kernel.org>
Cc: Lee Jones <lee.jones@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/regulator/core.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8a2ae3ab348cce44120667277c2198f10cc348b1

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-90360 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-90360

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: unknown
  Paranoid ActionableScore: 1

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).