CVE-2026-45926

Analyzed Analyzed - Analysis Complete

Memory Leak in Linux Kernel PWM Subsystem

Publication date: 2026-05-27

Last updated on: 2026-06-25

Assigner: kernel.org

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().

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-27

Last Modified

2026-06-25

Generated

2026-07-07

AI Q&A

2026-05-27

EPSS Evaluated

2026-07-05

NVD

CVE-2026-45926

EUVD

EUVD-2026-32392

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 6.19 (inc) to 6.19.4 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-401	The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

Attack-Flow Graph

Executive Summary

This vulnerability exists in the Linux kernel's Rust PWM (Pulse Width Modulation) driver. Specifically, when initializing a PWM chip using the function pwmchip_alloc(), the allocated device holds an initial reference that must be properly released if an error occurs during initialization.

If the function __pinned_init() fails during initialization, the allocated pwm_chip object is not properly released because the error path does not call pwmchip_put(). This results in a potential memory leak where allocated resources are not freed.

Impact Analysis

The primary impact of this vulnerability is a potential memory leak in the Linux kernel when initializing PWM chips. Over time, repeated failures in initialization could cause increased memory consumption, potentially leading to degraded system performance or instability.

Hi! I’m here to help you understand CVE-2026-45926. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70