Service interrupt via GRF node reference leak
Published Feb 26, 2025 · Updated May 11, 2026
Device-node reference leakage in the Rockchip GRF driver in Linux 4.11 through 5.18.3 allows local users to cause a service interrupt. rockchip_grf_init calls of_find_matching_node_and_match, which increments the matched node's reference count, but omits of_node_put after consuming the node. Exposure requires the affected Rockchip GRF initialization path and a matching Device Tree node; public sources identify no user-controlled trigger.
Summary
What happened
Device-node reference leakage in the Rockchip GRF driver in Linux 4.11 through 5.18.3 allows local users to cause a service interrupt. rockchip_grf_init calls of_find_matching_node_and_match, which increments the matched node's reference count, but omits of_node_put after consuming the node. Exposure requires the affected Rockchip GRF initialization path and a matching Device Tree node; public sources identify no user-controlled trigger.
The record
- CVE
- CVE-2022-49382
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- 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=4.11
- Affected versionversion=4c58063d4258f6beb4fd5647db6b58f49e337c8f <042571fe1d171773655ad706715ecc865913d9a4
- Affected versionversion=4c58063d4258f6beb4fd5647db6b58f49e337c8f <28133325526b92921f3269fdf97a20d90b92b217
- Affected versionversion=4c58063d4258f6beb4fd5647db6b58f49e337c8f <5b3e990f85eb034faa461e691e719e8ce9e2a3c8
- Affected versionversion=4c58063d4258f6beb4fd5647db6b58f49e337c8f <69a30b2ed620c2206cbbd1e9c112e4fc584e02bd
- Affected versionversion=4c58063d4258f6beb4fd5647db6b58f49e337c8f <8f64e84924604bb969ee1fbc4b8d7d09b9214889
- Affected versionversion=4c58063d4258f6beb4fd5647db6b58f49e337c8f <9b59588d8be91c96bfb0371e912ceb4f16315dbf
- Affected versionversion=4c58063d4258f6beb4fd5647db6b58f49e337c8f <aab25b669cb9fd3698c2631be4435f4fe92d9e59
- Affected versionversion=4c58063d4258f6beb4fd5647db6b58f49e337c8f <d5422f323858cad3ac3581075f9a3a5e0d41c0d8
What conditions does exploitation require?
What is affected?
Published CVSS scores
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