CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's Rockchip GPIO driver, which has issues related to resource leaks and improper teardown during driver removal. Specifically, it can lead to a panic due to an unregistered chained IRQ handler and memory leaks from unfreed debounce clocks and IRQ domains. System administrators and developers working with Linux kernel modules, particularly those involving Rockchip hardware, should prioritize addressing this vulnerability to ensure system stability and resource management.
Original NVD 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]
Related CVEs
Other vulnerabilities affecting the same vendor(s)