Kernel reference leak via unreleased IRQ parent
Published Dec 30, 2025 · Updated Dec 30, 2025
Resource leak in the STM32 pinctrl driver in Linux allows attackers to leak device-tree node references via unspecified vectors. The stm32_pctrl_get_irq_domain function calls of_irq_find_parent, which increments the returned node's reference count, without a matching of_node_put after lookup. Published records do not identify an attacker-controlled trigger or establish that the leak can exhaust memory or interrupt service.
Summary
What happened
Resource leak in the STM32 pinctrl driver in Linux allows attackers to leak device-tree node references via unspecified vectors. The stm32_pctrl_get_irq_domain function calls of_irq_find_parent, which increments the returned node's reference count, without a matching of_node_put after lookup. Published records do not identify an attacker-controlled trigger or establish that the leak can exhaust memory or interrupt service.
The record
- CVE
- CVE-2023-54205
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.2
- Affected versionversion=d86f4d71e42a9fa1866f030074e54d7571d16ec1 <601be03fa8b81747a154bdef9b559411a5b921e8
- Affected versionversion=d86f4d71e42a9fa1866f030074e54d7571d16ec1 <8ab860dd8717a7e4a143988885fea0d7e5a9412e
- Affected versionversion=d86f4d71e42a9fa1866f030074e54d7571d16ec1 <95ab6d7905ebb52dc2ed6357c38e536753824068
- Affected versionversion=d86f4d71e42a9fa1866f030074e54d7571d16ec1 <9ae053d1eb87875d56f95b6a123a69827225a70e
- Affected versionversion=d86f4d71e42a9fa1866f030074e54d7571d16ec1 <af54707c0ccab52b3d532402436ea101011a9299
- Affected versionversion=d86f4d71e42a9fa1866f030074e54d7571d16ec1 <dcef18c8ac40aa85bb339f64c1dd31dd458b06fb
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo