CVE-2026-80648
Received Received - Intake

NULL Pointer Dereference in Linux Kernel Pinctrl Subsystem

Vulnerability report for CVE-2026-80648, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-28

Last updated on: 2026-08-28

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-28
Last Modified
2026-08-28
Generated
2026-09-17
AI Q&A
2026-08-28
EPSS Evaluated
2026-09-15
NVD
EUVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Linux kernel vulnerability in the pinctrl subsystem for Spacemit SoCs. The function spacemit_pin_set_config incorrectly checks the pin ID variable instead of the pin descriptor pointer for NULL. This causes valid pin 0 to be rejected, leading to ignored PAD configuration writes for the first pin in every group. On K3 Pico-ITX boards, this affects the GMAC RGMII group's drive-strength and bias settings.

Detection Guidance

This vulnerability is specific to the Linux kernel's pinctrl subsystem for Spacemit SoCs. Detection requires checking kernel logs for failed PAD configuration writes or examining the spacemit_pin_set_config function in the kernel source. No network-specific detection commands are applicable.

Impact Analysis

If you use a Linux system with Spacemit SoCs (like K3 Pico-ITX boards), this vulnerability may cause network interface configuration issues. Specifically, the GMAC RGMII group's settings (drive-strength, bias) could be silently ignored, potentially leading to unstable or incorrect network performance.

Compliance Impact

This vulnerability does not directly affect compliance with standards like GDPR or HIPAA. It involves a NULL pointer check error in the Linux kernel's pinctrl subsystem, which could lead to incorrect pin configuration but does not involve data exposure or privacy violations.

Mitigation Strategies

Apply the latest Linux kernel update that includes the fix for CVE-2026-80648. If using a custom kernel, patch the spacemit_pin_set_config function to check the 'spin' variable instead of 'pin' for NULL. Reboot the system after applying changes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-80648. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart