[CVE-2026-98883][LOW] serial: 8250_port: recognize UPIO_AU [ Upstream

[CVE-2026-98883][LOW] serial: 8250_port: recognize UPIO_AU [ Upstream

[AL-KERNEL]

CVE: CVE-2026-98883
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: serial: 8250_port: recognize UPIO_AU [ Upstream
Commit: 9f67997353caa29c6a080789a1fb6e01fb50c118
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9f67997353caa29c6a080789a1fb6e01fb50c118
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98883
Analysis date: Mon, 26 Oct 2026 20:56:27 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
The 8250 probe incorrectly warns for an already configured `UPIO_AU` port, with no demonstrated memory corruption, authorization bypass, or attacker-reachable security impact.

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

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

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-98883	LOW	https://www.kernelcve.org/list/?q=CVE-2026-98883 CHECK WITH IMPACT FROM ORIG NN LOW | 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:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';CWE-684;BEST CVSS score: '1.9';DESCR 'The serial 8250 setup path does not recognize UPIO_AU and emits an unsupported UART WARN while probing MIPS Alchemy systems. The UART parameters are already initialized by au_platform_setup, so the demonstrated primitive is only a spurious warning and not memory corruption. Availability impact is normally negligible, although panic_on_warn can turn the warning into a boot failure or kernel panic on an affected platform. For the CVSS the PR:H value reflects that reliable triggering requires control over kernel or platform configuration and device probing rather than ordinary local user access. The issue is not network reachable and there is no supported confidentiality or integrity impact. Automated impact decision path. The original SimpleNet classifier selected LOW. The primary LLM estimated paranoid CVSS 1.9 and the production ActionableScore returned 0 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. No severity changing production threshold or specialist override was recorded. 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. The independent weaker Aegis shadow evaluated CVSS 0.0 and ActionableScore 0 with primitive class NONE and manual review REQUIRED. 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	WARNONLY PRINTF-TTY SIMPLEFIX HARDWARE LINUS 	-	-	checked

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

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

1. ActionableScore

* Raw base score: 0.
* Conservative score: 0; no floor or cap applied.
* Raw paranoid score: 0.
* Paranoid score: 0; `WARN()` alone receives no crash point.
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

* +0: The missing `UPIO_AU` switch case reaches only the default `WARN()`; the patch does not show an invalid access, overwrite, UAF, state corruption, or authorization failure.
* +0: A `panic_on_warn` configuration could convert the warning into a boot failure, but no such configuration or observed fatal outcome is supplied.
* No hardware or privilege penalty was applied because the score already has no positive security signal.
* B5-R does not apply: there is no heap OOB write, retry-accumulated offset, or later consumption of corrupted state.
* B3-PENDING and B4-PENDING do not apply: there is neither a shared-backing write nor a DENY-to-ALLOW authorization change.
* No confidentiality, integrity, remote-reachability, or reliable host-DoS points are supported.

3. Reachability analysis

The warning occurs during platform-driver probing on MIPS Alchemy hardware using `UPIO_AU`. The supplied evidence does not establish an attacker-invocable interface or ordinary-user trigger. Trigger privilege is therefore unresolved rather than positively host-admin-only. No namespace capability, prior delegation, race, retry sequence, or network path is involved.

4. Primitive and severity reading

The defect is an omitted recognized UART type in a setup switch. Existing parameters were already initialized by `au_platform_setup()`, and the fix merely accepts that type without changing state. The shown effect is a spurious warning. A panic under `panic_on_warn` is configuration-dependent and not enough to establish a security primitive. `PrimitiveClass=NONE`, with no Important candidate and no reason to block automatic downgrade.

5. One-sentence report phrase

The 8250 probe incorrectly warns for an already configured `UPIO_AU` port, with no demonstrated memory corruption, authorization bypass, or attacker-reachable security impact.

6. Manual review advice

NO MANUAL CHECK NEEDED

The patch and call path support only a compatibility-warning fix.

7. Call-site confidence

Call-site confidence: high

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

Patch: serial: 8250_port: recognize UPIO_AU [ Upstream
Commit: 9f67997353caa29c6a080789a1fb6e01fb50c118
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9f67997353caa29c6a080789a1fb6e01fb50c118

Changed files:
  drivers/tty/serial/8250/8250_port.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=9f67997353caa29c6a080789a1fb6e01fb50c118

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

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

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:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS score: 1.9

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