[CVE-2026-80648][LOW] pinctrl: spacemit: fix NULL check in spacemit_pin_set_config [ Upstream

[CVE-2026-80648][LOW] pinctrl: spacemit: fix NULL check in spacemit_pin_set_config [ Upstream

[AL-KERNEL]

CVE: CVE-2026-80648
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: pinctrl: spacemit: fix NULL check in spacemit_pin_set_config [ Upstream
Commit: 7a551951ebeb5b3f05bdb04a73d4593869c984c4
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7a551951ebeb5b3f05bdb04a73d4593869c984c4
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80648
Analysis date: Fri, 28 Aug 2026 07:01:41 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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

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

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

CVE-2026-80648	LOW	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:H/UI:N/S:U/C:N/I:L/A:H';**CWE-476;CWE-754;*CWE-20;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:L';BEST CVSS score: '4.7';DESCR 'spacemit_pin_set_config used the wrong NULL check after spacemit_get_pin. It checked the numeric pin id instead of the returned spin pointer, so valid pin 0 could be rejected and its PAD configuration could be skipped. For invalid nonzero pin ids, spacemit_get_pin may return NULL and the later spin pin dereference can crash the kernel. For the CVSS the PR:H is used because reliable triggering normally requires control over platform pin configuration, device tree data, overlays, or another privileged hardware configuration path. The issue is not network reachable and is not triggered by packet traffic. Impact is mainly incorrect pin configuration and possible denial of service through a NULL pointer dereference. No UAF, OOB write, arbitrary write, information leak, or realistic privilege escalation primitive is visible from the patch context.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 0)  SKIP CVE-2026-80648 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: url YES  NO NO unknown 	MAYBE	IMPROVEONLY 	-	-	guess

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

ActionableScore=0

1. ActionableScore
* Conservative score: 0
* Paranoid score: 0
* Final recommended bucket: **Ordinary Moderate / Low-like**::

2. Signal breakdown
* Weak corruption candidate: +0. The NULL dereference is an invalid pointer dereference, not UAF, OOB write, type confusion, refcount abuse, or attacker controlled memory corruption.
* Availability concern: +1. Invalid nonzero pin ids may make `spacemit_get_pin()` return NULL and then `spin->pin` can crash the kernel.
* Integrity or configuration correctness concern: +1. Valid pin 0 was incorrectly rejected, so PAD configuration such as drive strength or bias could be skipped.
* Requires admin or privileged hardware configuration path: -2. Reliable triggering normally requires control over platform pin configuration, device tree data, overlays, or another privileged SoC configuration path.
* Rare hardware or platform specific path: -1. This is specific to SpacemiT pinctrl hardware and not a broad default Linux attack surface.
* Floor applied: score does not go below 0.

3. Reachability analysis
The bug is local and platform specific. It is not network reachable and is not triggered by packet traffic. A normal unprivileged local user typically cannot choose arbitrary SoC pin ids or modify pinctrl configuration. Containers and namespaces usually do not reduce the privilege requirement unless the product exposes trusted pinctrl or device tree overlay controls to less privileged workloads. Call-site confidence: medium, because the changed function and immediate failure mode are visible, but broader product-specific runtime exposure is not shown.

4. Severity interpretation
This behaves more like a Low-like or ordinary Moderate correctness and reliability issue than an actionable kernel security issue. The realistic impact is skipped hardware PAD configuration for valid pin 0 and possible local privileged DoS through NULL pointer dereference for invalid pin ids. There is no evidence of UAF, stale object reuse, write-after-free, OOB write, arbitrary write, information disclosure, or privilege escalation.

5. One-sentence report phrase
A wrong NULL check in spacemit_pin_set_config can skip PAD configuration for valid pin 0 and can cause a NULL pointer dereference for invalid pin ids, but triggering normally requires privileged platform pin configuration control and the issue is not network reachable.

6. Manual review recommendation
NO MANUAL CHECK REQUIRED COULD BE AUTOCLOSED
Reason: this is a privileged, platform-specific NULL dereference and configuration correctness bug with no supported LPE, information leak, or strong memory corruption primitive.

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

Patch: pinctrl: spacemit: fix NULL check in spacemit_pin_set_config [ Upstream
Commit: 7a551951ebeb5b3f05bdb04a73d4593869c984c4
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7a551951ebeb5b3f05bdb04a73d4593869c984c4

Changed files:
  drivers/pinctrl/spacemit/pinctrl-k1.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=7a551951ebeb5b3f05bdb04a73d4593869c984c4

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

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

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