CVE-2026-64241
Received Received - Intake

Resource Leak in Linux Kernel GPIO Rockchip Driver

Publication date: 2026-07-24

Last updated on: 2026-07-24

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: gpio: rockchip: teardown bugs and resource leaks Address several teardown issues and resource leaks in the driver's remove path and error handling: 1. Debounce clock reference leak: The debounce clock (bank->db_clk) is obtained using of_clk_get() which increments the clock's reference count, but clk_put() is never called. Register a devm action to cleanly release it on unbind. Note that of_clk_get(..., 1) remains necessary over devm_clk_get() because the DT binding does not define clock-names, precluding name-based lookup. 2. Unregistered chained IRQ handler: The chained IRQ handler is not disconnected in remove(). If a stray interrupt fires after the driver is removed, the kernel attempts to execute a stale handler, leading to a panic. Fix this by clearing the handler in remove(). 3. IRQ domain leak: The linear IRQ domain and its generic chips are allocated manually during probe but never removed. Remove the IRQ domain during driver teardown to free the associated generic chips and mappings. [Bartosz: don't emit an error message on devres allocation failure]

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-24
Last Modified
2026-07-24
Generated
2026-07-24
AI Q&A
2026-07-24
EPSS Evaluated
N/A
NVD
CVE-2026-64241
EUVD
EUVD-2026-48650

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
rockchip gpio *
rockchip linux_kernel *

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 vulnerability involves resource leaks and improper cleanup in the Linux kernel's Rockchip GPIO driver. It includes a clock reference leak, an unregistered chained IRQ handler, and an IRQ domain leak. These issues can cause system instability or crashes if not properly handled during driver removal.

Detection Guidance

This vulnerability is specific to the Linux kernel's GPIO driver for Rockchip hardware and does not have network-based detection methods. Detection involves checking kernel logs for crashes or panics related to GPIO interrupts or resource leaks. Monitor dmesg for errors like 'stale handler' or 'panic' after driver removal. Check for resource leaks using kernel debug tools like 'slabtop' or 'cat /proc/slabinfo' to identify unreleased clock references or IRQ domains.

Impact Analysis

This vulnerability may lead to system crashes or instability if a stray interrupt fires after the driver is removed. It could also cause resource exhaustion due to unreleased clock references, potentially affecting system performance or causing unexpected behavior.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. It involves resource leaks and improper teardown in the Linux kernel's Rockchip GPIO driver, which could lead to system instability or crashes but does not involve data handling or privacy issues.

Mitigation Strategies

Apply the latest kernel update that includes the fix for CVE-2026-64241. If updating is not immediately possible, avoid unloading the Rockchip GPIO driver while the system is running. Monitor system logs for crashes or panics related to GPIO interrupts. Ensure no critical processes depend on the Rockchip GPIO functionality during driver updates.

Chat Assistant

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

EPSS Chart