Local denial of service via device-node reference leak
Published Feb 26, 2025 · Updated May 11, 2026
Reference-count leak in the Linux kernel PFUZE100 regulator driver from 3.12 allows local users to exhaust kernel memory. pfuze_parse_regulators_dt obtains an incremented device-tree node reference with of_node_get but omits the matching of_node_put after the node is no longer needed. Low-privileged local access and use of the affected regulator path are required; repeated triggering can deny service by consuming kernel memory.
Summary
What happened
Reference-count leak in the Linux kernel PFUZE100 regulator driver from 3.12 allows local users to exhaust kernel memory. pfuze_parse_regulators_dt obtains an incremented device-tree node reference with of_node_get but omits the matching of_node_put after the node is no longer needed. Low-privileged local access and use of the affected regulator path are required; repeated triggering can deny service by consuming kernel memory.
The record
- CVE
- CVE-2022-49481
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=3.12
- Affected versionversion=3784b6d64dc52ed3fbebad61a85ab9b7a687a167 <0be5d9da5743b9825a95baec85a67500b2c1d362
- Affected versionversion=3784b6d64dc52ed3fbebad61a85ab9b7a687a167 <49d785baeb91568332197be356d138e5e59c7ddb
- Affected versionversion=3784b6d64dc52ed3fbebad61a85ab9b7a687a167 <56ab0c01027492cd161c64148e1dc892c56887ad
- Affected versionversion=3784b6d64dc52ed3fbebad61a85ab9b7a687a167 <671be14fc31374b1a10a3abd93db6a8480838fc9
- Affected versionversion=3784b6d64dc52ed3fbebad61a85ab9b7a687a167 <6ca675f4abbc74bc991d154a1ecc8b384dc2aae4
- Affected versionversion=3784b6d64dc52ed3fbebad61a85ab9b7a687a167 <984cfef0675ed7398814e14af2c5323911723e1c
- Affected versionversion=3784b6d64dc52ed3fbebad61a85ab9b7a687a167 <9f564e29a51210a49df3d925117777c157a17d6d
- Affected versionversion=3784b6d64dc52ed3fbebad61a85ab9b7a687a167 <afaa7b933ef00a2d3262f4d1252087613fb5c06d
- Affected versionversion=3784b6d64dc52ed3fbebad61a85ab9b7a687a167 <b74c0dd9179d21b7260260e075d597b23970100c
What conditions does exploitation require?
What is affected?
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
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