VulnerabilityPublished 24 Jul 2026Updated 21 Oct 2026

CVE-2026-64241: Linux kernel · gpio: rockchip: teardown bugs and resource leaks

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in cdc603ce3118232712ba443dd8b414d8f25ca467 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in cdc603ce3118232712ba443dd8b414d8f25ca467, 9500077678230e36d22bf16d2b9539c13e59a801, 77b6ff33c8f5642f7e7c1ca691857218683264fd +2

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 936ee2675eee1faca0dcdfa79165c7990422e0fc, < cdc603ce3118232712ba443dd8b414d8f25ca467	Fixed in cdc603ce3118232712ba443dd8b414d8f25ca467
LinuxLinux	Affected ≥ 936ee2675eee1faca0dcdfa79165c7990422e0fc, < 9500077678230e36d22bf16d2b9539c13e59a801	Fixed in 9500077678230e36d22bf16d2b9539c13e59a801
LinuxLinux	Affected ≥ 936ee2675eee1faca0dcdfa79165c7990422e0fc, < 77b6ff33c8f5642f7e7c1ca691857218683264fd	Fixed in 77b6ff33c8f5642f7e7c1ca691857218683264fd
LinuxLinux	Affected ≥ 936ee2675eee1faca0dcdfa79165c7990422e0fc, < 7f945f7f10f442270518dfd768d230227c495fcf	Fixed in 7f945f7f10f442270518dfd768d230227c495fcf
LinuxLinux	Affected ≥ 936ee2675eee1faca0dcdfa79165c7990422e0fc, < 6be81e77e1748665d7ddab9128ff1d35eb75b87d	Fixed in 6be81e77e1748665d7ddab9128ff1d35eb75b87d
LinuxLinux	Affected =5.15	Fixed in–

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]

References

Community reviews

Loading reviews…