pinctrl: spacemit: fix NULL check in spacemit_pin_set_config (CVE-2026-80648) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80648

pinctrl: spacemit: fix NULL check in spacemit_pin_set_config

Answer in brief

CVE-2026-80648 records a Unknown severity vulnerability in pinctrl: spacemit: fix NULL check in spacemit_pin_set_config. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 28, 2026Updated Aug 28, 2026Source checked Aug 28, 2026First seen by HOL Aug 28, 2026Material review Aug 28, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=a83c29e1d145cca5240952100acd1cd60f25fb5f <7a551951ebeb5b3f05bdb04a73d4593869c984c4 \|\| >=a83c29e1d145cca5240952100acd1cd60f25fb5f <d3b53f0eda26e442ff97016ad4a0724db8fd3781 \|\| >=a83c29e1d145cca5240952100acd1cd60f25fb5f <09c816e5c4d3a8d6d6e4b7537433e5e98505d934	7a551951ebeb5b3f05bdb04a73d4593869c984c4, d3b53f0eda26e442ff97016ad4a0724db8fd3781, 09c816e5c4d3a8d6d6e4b7537433e5e98505d934
Linux/Linuxgeneric	6.13	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 7a551951ebeb5b3f05bdb04a73d4593869c984c4 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 28, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: pinctrl: spacemit: fix NULL check in spacemit_pin_set_config spacemit_pin_set_config() looks up the per-pin descriptor with spacemit_get_pin() then checks the wrong variable for failure: const struct spacemit_pin *spin = spacemit_get_pin(pctrl, pin); ... if (!pin) return -EINVAL; reg = spacemit_pin_to_reg(pctrl, spin->pin); pin is an unsigned int pin id, where 0 (GPIO_0 / gmac0_rxdv on K3) is a valid pin, so rejecting it here drops the PAD config write for the first pin of every group. On K3 Pico-ITX the GMAC RGMII group lists pin 0 as its first entry, so its drive-strength / bias configuration was silently ignored. The intended guard is against spacemit_get_pin() returning NULL when the pin id isn't in the SoC's pin table. Check spin instead, which both restores PAD setup for pin 0 and prevents a NULL deref on spin->pin.

Quoted source text, attributed separately from HOL analysis.