CVE-2026-64241
Last modified
CVE-2026-64241 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
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]
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 936ee2675eee1faca0dcdfa79165c7990422e0fc, < cdc603ce3118232712ba443dd8b414d8f25ca467; >= 936ee2675eee1faca0dcdfa79165c7990422e0fc, < 7f945f7f10f442270518dfd768d230227c495fcf; >= 936ee2675eee1faca0dcdfa79165c7990422e0fc, < 6be81e77e1748665d7ddab9128ff1d35eb75b87d; >= 936ee2675eee1faca0dcdfa79165c7990422e0fc, < 9500077678230e36d22bf16d2b9539c13e59a801 |
| Linux | Linux | 5.15 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-64241?
How severe is CVE-2026-64241?
How do I fix CVE-2026-64241?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64236In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64237In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64238In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64239In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6424Use-after-free vulnerability in ESET Linux products potentia…6.7
- CVE-2026-64240In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64242In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64243In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64244In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64245In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64246In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64247In the Linux kernel, the following vulnerability has been re…8.4
Are you affected by CVE-2026-64241?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
