[CVE-2026-98675][LOW] iio: adc: ade9000: handle Phase C dip events in IRQ1 handler

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-98675
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: iio: adc: ade9000: handle Phase C dip events in IRQ1 handler
Commit: f73b94acc7ec81f9c49feb87f649ba5a80a0905c
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f73b94acc7ec81f9c49feb87f649ba5a80a0905c
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98675
Analysis date: Mon, 19 Oct 2026 02:49:44 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
An off by one event scan bound prevents the ADE9000 IRQ1 handler from reporting Phase C voltage dip events, but it does not establish memory corruption, authorization bypass, kernel crash, or privilege escalation.

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

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

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-98675	LOW	https://www.kernelcve.org/list/?q=CVE-2026-98675 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT LOW AEGIS_AS=0 LEGACY=LOW RESULT=SAME (final reconciliation agrees; DECISION: both LOW)	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L';CWE-193;CWE-682;BEST CVSS score: '3.5';DESCR 'An off by one upper bound in the ADE9000 STATUS1 event scan excludes bit 25, so Phase C voltage dip events are not reported by the IRQ1 handler. The issue is a logic error and does not provide an out of bounds access, use after free, invalid pointer dereference, or other memory corruption primitive. Impact is limited to missing measurement telemetry and potentially incorrect behavior by software that relies on Phase C dip notifications. For the CVSS the PR:N value is used because generating the physical voltage event does not require privileges in the target operating system. The attack vector is physical rather than local or network reachable because an attacker would need influence over the monitored electrical input or attached measurement environment. There is no demonstrated kernel crash, information disclosure, privilege escalation, or host wide denial of service. Automated impact decision path. The original SimpleNet classifier selected MODERATE. The primary LLM estimated paranoid CVSS 3.5 and the production ActionableScore returned 0 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage MODERATE to LOW because the CVSS score, vector or bug class threshold rule was applied. The legacy KP specialist has no review artifact for this run. The legacy FD or DH downgrade specialist has no review artifact for this run. Exact triggered rule markers were DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_GUESSCVSS. The independent weaker Aegis shadow evaluated CVSS 2.4 and ActionableScore 0 with primitive class NONE and manual review NO. Its independently reconciled impact was LOW. The shadow agreed with the final production impact and aggregation did not change that impact. The final reported impact is LOW.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0)	MAYBE	SIMPLEFIX LINUS  DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_GUESSCVSS	-	-	checked

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

ActionableScore=0
PrimitiveClass=NONE
RealUAF=NO
HostAdminRequired=NO
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES
RequiresHostUID0=NO
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO

1. ActionableScore

* Raw conservative score: 0
* Conservative score: 0
* Raw paranoid score: 0
* Paranoid score: 0
* No floor or cap was applied.
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

* +0 Logic error. The exclusive upper bound of 25 prevents IRQ1 scanning from processing `ADE9000_ST1_DIPC_BIT` at bit 25.
* +0 Missing telemetry. Phase C voltage dip events are not reported, but no kernel crash, host-wide outage, persistent resource loss, or protected-state modification is established.
* +0 No corruption primitive. The patch does not establish an OOB access, UAF, invalid pointer, overwrite, shared-backing modification, stale active state, or retry-accumulated write.
* +0 No authorization primitive. No access-control guard changes from DENY to ALLOW.
* No remote, local-unprivileged kernel API, namespace-boundary, confidentiality, privilege-escalation, or practical exploit-chain points were awarded.
* B5-R does not apply because there is no heap OOB write, accumulating retry index, or later consumption of corrupted structured state.
* B3-PENDING does not apply because there is no write to shared or file-backed storage.
* V33 and V34 do not apply because there is no attacker-influenced active structured-state corruption or downstream privileged consumer.
* B4-PENDING does not apply because no authorization decision or protected resource is involved.

3. Reachability analysis

The affected path requires the ADE9000 hardware and its IIO driver. A Phase C voltage dip is a physical input event and does not require host UID 0 or host-administrator privileges to occur. However, the evidence does not establish a software-controlled attacker interface for generating the event.

There is no network, namespace, ioctl, or delegated-interface trigger shown. No race or retry sequence is involved. The relevant prerequisite is the presence of ADE9000 hardware and reliance on Phase C dip notifications.

4. Primitive and severity interpretation

The exact defect is an off-by-one exclusive scan bound that omits one valid status bit. It is a passive event-reporting logic error, not a memory-safety, lifetime, ownership, authorization, or security-boundary violation.

The demonstrated consequence is loss of Phase C dip telemetry. A downstream monitoring or control application could make an incorrect decision because the event is absent, but no protected-state modification, kernel failure, cross-authority effect, or host-wide availability impact is established.

`PrimitiveClass=NONE` is appropriate because no actionable kernel-security primitive exists. `ImportantCandidate=NO` and `AutoDowngradeAllowed=YES` follow because none of the Important-preserving profiles are satisfied.

5. One-sentence report phrase

An off by one event scan bound prevents the ADE9000 IRQ1 handler from reporting Phase C voltage dip events, but it does not establish memory corruption, authorization bypass, kernel crash, or privilege escalation.

6. Manual review recommendation

NO MANUAL CHECK NEEDED

The patch fixes a bounded telemetry omission with no demonstrated kernel-security primitive. Additional operational review is only relevant if Phase C dip reporting is used by safety-critical or protection logic.

7. Call-site confidence

Call-site confidence: high

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

Patch: iio: adc: ade9000: handle Phase C dip events in IRQ1 handler
Commit: f73b94acc7ec81f9c49feb87f649ba5a80a0905c
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f73b94acc7ec81f9c49feb87f649ba5a80a0905c

Commit description:

ADE9000_ST1_CROSSING_DEPTH is the exclusive upper bound for scanning the
STATUS1 event bits, so a value of 25 left out the highest event bit,
ADE9000_ST1_DIPC_BIT (bit 25). Phase C dip events were never reported.

Bump the value to 26 so bit 25 is scanned.

Fixes: 81de7b4 ("iio: adc: add ade9000 support")
Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: <Stable@vger.kernel.org>
Signed-off-by: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/iio/adc/ade9000.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=f73b94acc7ec81f9c49feb87f649ba5a80a0905c

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

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

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: Not available
  The Best / paranoid CVSS vector: AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
  The Best / paranoid CVSS score: 3.5

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: 0

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).