CVE-2026-92482

pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip

Published Sep 17, 2026 CVSS n/a EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip

The gpio_chip is allocated with device-managed memory but registered with
the non-managed gpiochip_add_data(). This was harmless while the drivers
were built-in, but once they can be built as modules and unbound/rmmod'd,
devm frees the gpio_chip's memory while it is still registered, causing a
use-after-free.

Register it with devm_gpiochip_add_data() so it shares the same
device-managed lifecycle, which also lets the manual gpiochip_remove()
error paths go away.

Analysis

AI-generated

Technical impact

The Mediatek pinctrl driver allocates the gpio_chip structure with device‑managed memory yet registers it using the non‑managed function gpiochip_add_data(). When the driver is unloaded as a module, the device‑managed memory is freed while the GPIO chip remains registered, leading to a use‑after‑free condition that can cause a kernel crash or memory corruption.

Affected Systems

The flaw exists in any Linux kernel that bundles the Mediatek pinctrl driver for Mediatek SoCs. Because no kernel version range is specified, all kernels before the applied patch could be impacted.

Risk and Exploitability

The EPSS score is below 1 % and the vulnerability is not listed in CISA’s KEV catalog, indicating a low exploitation probability. The attack vector requires the ability to unload or reload the affected module, a capability that is typically restricted to privileged users; this inference is made from the description that drivers can be built as modules and unbound. The primary risk is a kernel crash, and memory corruption could potentially lead to more severe outcomes if an attacker is able to exploit the use‑after‑free.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the kernel patch that registers the gpio_chip with devm_gpiochip_add_data(), ensuring the chip’s lifecycle matches device allocation.
  • Rebuild and deploy the updated Mediatek pinctrl module so the driver no longer uses the legacy registration path.
  • If a patch cannot be applied immediately, avoid unloading the medi prossed pinctrl driver or restrict module removal for that driver to prevent the use‑after‑free scenario.

Generated by OpenCVE AI on September 19, 2026 at 12:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4904-1 linux-6.12 security update
Debian DLA Debian DLA DLA-4906-1 linux security update
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip The gpio_chip is allocated with device-managed memory but registered with the non-managed gpiochip_add_data(). This was harmless while the drivers were built-in, but once they can be built as modules and unbound/rmmod'd, devm frees the gpio_chip's memory while it is still registered, causing a use-after-free. Register it with devm_gpiochip_add_data() so it shares the same device-managed lifecycle, which also lets the manual gpiochip_remove() error paths go away.
Title pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 30, 2026, 12:35 PM
Reserved
Sep 16, 2026, 12:21 PM
Status
Received
Published
Sep 17, 2026, 5:17 PM
Modified
Oct 30, 2026, 1:20 PM