Service interruption via leaked device-tree node references
Published Jun 18, 2025 · Updated May 11, 2026
Resource leak in the ARM Broadcom Kona SMC initialization path in affected Linux kernels allows local users to interrupt service. bcm_kona_smc_init retains the device-tree node reference returned by of_find_matching_node because it omits the matching of_node_put after the node is no longer needed. Exploitation requires local low-privileged access and an ARM system using the Broadcom Kona SMC path; the documented consequence is availability loss, not data access or modification.
Summary
What happened
Resource leak in the ARM Broadcom Kona SMC initialization path in affected Linux kernels allows local users to interrupt service. bcm_kona_smc_init retains the device-tree node reference returned by of_find_matching_node because it omits the matching of_node_put after the node is no longer needed. Exploitation requires local low-privileged access and an ARM system using the Broadcom Kona SMC path; the documented consequence is availability loss, not data access or modification.
The record
- CVE
- CVE-2022-50207
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 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.10
- Affected versionversion=b8eb35fd594aa5b635e329d5c8efab8aaceb8619 <02b658bfb26452f2c13e4577a13ab802f89a6642
- Affected versionversion=b8eb35fd594aa5b635e329d5c8efab8aaceb8619 <5afe042c889437de83f38a9d73d145742fb4f65f
- Affected versionversion=b8eb35fd594aa5b635e329d5c8efab8aaceb8619 <62d719d31ec667276d7375b64542b080cf187797
- Affected versionversion=b8eb35fd594aa5b635e329d5c8efab8aaceb8619 <75866df2b1d673df5b7781e565ada753a7895f04
- Affected versionversion=b8eb35fd594aa5b635e329d5c8efab8aaceb8619 <91e7f04f53e680bc72f0a9a5c682ab652100b9c8
- Affected versionversion=b8eb35fd594aa5b635e329d5c8efab8aaceb8619 <bc7f487395f208fd9af69e9a807815e10435aba7
- Affected versionversion=b8eb35fd594aa5b635e329d5c8efab8aaceb8619 <c6964cb9ac7a43bf78e7d60126e2722992de2ea1
- Affected versionversion=b8eb35fd594aa5b635e329d5c8efab8aaceb8619 <cb23389a2458c2e4bfd6c86a513cbbe1c4d35e76
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
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