CVE-2026-43138

reset: gpio: suppress bind attributes in sysfs

Published May 6, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

reset: gpio: suppress bind attributes in sysfs

This is a special device that's created dynamically and is supposed to
stay in memory forever. We also currently don't have a devlink between
it and the actual reset consumer. Suppress sysfs bind attributes so that
user-space can't unbind the device because - as of now - it will cause a
use-after-free splat from any user that puts the reset control handle.

Analysis

AI-generated

Technical impact

The Linux kernel’s reset GPIO driver creates a dynamic device that is meant to persist in memory. The driver exposes sysfs bind attributes, allowing user space to unbind the device. If an attacker unbinds it, the kernel dereferences freed memory, resulting in a use‑after‑free condition. This can corrupt data, crash the kernel, or provide a foothold for arbitrary code execution. The underlying weakness is a use‑after‑free condition (CWE‑416), compounded by improper event handling (CWE‑825).

Affected Systems

All Linux kernel builds that contain the unprotected reset GPIO sysfs bind attributes are affected. This includes any release prior to the patch that suppresses those attributes; there is no vendor‑specific restriction since the vulnerability resides in the core kernel code.

Risk and Exploitability

Exploitation requires the ability to write to the sysfs bind attribute, which typically demands local user privileges and access to the device’s directory under /sys. The attack vector is inferred from the description of unbinding the device via user space. The CVSS score is 7.8, and the EPSS score is <1%, indicating a low likelihood of exploitation in the wild. The vulnerability is not listed in the CISA KEV catalog. As a result, the risk remains limited to local users with write access to the reset device’s sysfs directory; remote exploitation without additional privilege escalation remains unlikely.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the kernel to a build that includes the patch suppressing reset GPIO sysfs bind attributes.
  • Verify that the reset GPIO device’s sysfs directory no longer exposes bind attributes and that write access is removed for non‑privileged users.
  • If an immediate kernel upgrade is not possible, apply strict filesystem permissions or enforce SELinux/AppArmor policies to deny write access to any bind attribute under the reset device’s sysfs path.

Generated by OpenCVE AI on May 12, 2026 at 23:02 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-416
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: reset: gpio: suppress bind attributes in sysfs This is a special device that's created dynamically and is supposed to stay in memory forever. We also currently don't have a devlink between it and the actual reset consumer. Suppress sysfs bind attributes so that user-space can't unbind the device because - as of now - it will cause a use-after-free splat from any user that puts the reset control handle.
Title reset: gpio: suppress bind attributes in sysfs
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
May 11, 2026, 10:18 PM
Reserved
May 1, 2026, 2:12 PM
Status
Analyzed
Published
May 6, 2026, 12:16 PM
Modified
Nov 11, 2026, 9:10 PM
Severity
Public date
May 6, 2026, 12:00 AM