# CVE-2026-80648: pinctrl: spacemit: fix NULL check in spacemit_pin_set_config

> A NULL pointer dereference in the Linux kernel pinctrl driver can cause a system crash when configuring specific pins.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** BELL-CVE-2026-80648, DEBIAN-CVE-2026-80648, GHSA-v3gv-j32h-qw62, UBUNTU-CVE-2026-80648

## What is CVE-2026-80648?

CVE-2026-80648 is a vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-80648?


## How do I fix CVE-2026-80648?

Apply the vendor's patch.

## Is CVE-2026-80648 being exploited?

There is no known exploitation of CVE-2026-80648 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80648 and fix it if it is affected.

What it is: CVE-2026-80648 is a vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80648 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80648/ (Markdown: https://insights.sbomify.com/CVE-2026-80648/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80648
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80648
- OSV: https://osv.dev/vulnerability/CVE-2026-80648

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80648/
Summaries are generated and may contain mistakes; the official description above is the record.