Description
In the Linux kernel, the following vulnerability has been resolved:

rust: pwm: Fix potential memory leak on init error

When initializing a PWM chip using pwmchip_alloc(), the allocated device
owns an initial reference that must be released on all error paths.

If __pinned_init() were to fail, the allocated pwm_chip would currently
leak because the error path returns without calling pwmchip_put().
Published: 2026-05-27
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The flaw resides in the Linux kernel’s PWM subsystem. When a PWM chip is allocated via pwmchip_alloc(), the allocation creates a pwm_chip structure with an initial reference count that must be released on all error paths. If the subsequent __pinned_init() fails, the code returns without calling pwmchip_put(), leaving that reference unreleased. Each failure therefore leaks memory, and repeated failure events can cause the kernel memory usage to grow until the system becomes unstable or unresponsive. The vulnerability does not provide direct code execution, but it can lead to a denial‑of‑service condition through resource exhaustion.

Affected Systems

The bug affects all Linux kernels that have not incorporated the patch commits shown in the advisory. No specific version constraints are published in the CVE record, so any system running a kernel version prior to the inclusion of the described fixes—identified in the commit logs—remains vulnerable. The issue applies to distributions that load the PWM subsystem, regardless of whether the kernel is running in user space or on embedded devices.

Risk and Exploitability

The impact is a classic resource‑management flaw (CWE‑401) and, based on the description, it is inferred that the likely attack vector requires the attacker to trigger PWM chip initialization failures locally. No remote exploit path is described. The vulnerability is not listed in CISA’s KEV catalog. Because the flaw can deplete kernel memory, the risk is moderate to high for systems that allow untrusted local users or services to allocate PWM chips. Successful exploitation would result in memory exhaustion and service interruption rather than direct code execution.

Generated by OpenCVE AI on May 27, 2026 at 19:01 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that contains the commits that fix the PWM memory leak, such as the latest stable release of the current kernel series.
  • If a kernel upgrade cannot be performed immediately, download the patch files from the commits referenced in the advisory, apply them to the kernel source tree, and rebuild and reinstall the kernel.
  • Restrict access to the pwmchip interface so that only privileged users or trusted services can request PWM chip allocation, thereby reducing the likelihood of an attacker triggering the failure path.
  • If the host does not require PWM functionality, compile the kernel with the PWM subsystem disabled to remove the vulnerable code path.

Generated by OpenCVE AI on May 27, 2026 at 19:01 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 27 May 2026 19:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-401

Wed, 27 May 2026 14:15:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: rust: pwm: Fix potential memory leak on init error When initializing a PWM chip using pwmchip_alloc(), the allocated device owns an initial reference that must be released on all error paths. If __pinned_init() were to fail, the allocated pwm_chip would currently leak because the error path returns without calling pwmchip_put().
Title rust: pwm: Fix potential memory leak on init error
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-05-27T12:17:45.351Z

Reserved: 2026-05-13T15:03:33.086Z

Link: CVE-2026-45926

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-05-27T14:17:08.473

Modified: 2026-05-27T14:48:03.013

Link: CVE-2026-45926

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-27T19:15:26Z

Weaknesses