Service interruption via probe-time reference leak
Published Feb 26, 2025 · Updated May 11, 2026
A reference leak in Linux kernel Broadcom STB power management allows local users to interrupt service during device probing. The brcmstb_pm_probe path calls of_find_matching_node() in brcmstb_init_sram but fails to release the returned device-tree node with of_node_put() after of_address_to_resource() takes its own reference. Reachability requires local access and the affected Broadcom STB driver path; published assessments identify availability impact only, without a disclosed crash or hang mode.
Summary
What happened
A reference leak in Linux kernel Broadcom STB power management allows local users to interrupt service during device probing. The brcmstb_pm_probe path calls of_find_matching_node() in brcmstb_init_sram but fails to release the returned device-tree node with of_node_put() after of_address_to_resource() takes its own reference. Reachability requires local access and the affected Broadcom STB driver path; published assessments identify availability impact only, without a disclosed crash or hang mode.
The record
- CVE
- CVE-2022-49678
- 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=0b741b8234c86065fb6954d32d427b3f7e14756f <10ba9d499a9fd82ed40897e734ba19870a879407
- Affected versionversion=0b741b8234c86065fb6954d32d427b3f7e14756f <30bbfeb480ae8b5ee43199d72417b232590440c2
- Affected versionversion=0b741b8234c86065fb6954d32d427b3f7e14756f <37d838de369b07b596c19ff3662bf0293fdb09ee
- Affected versionversion=0b741b8234c86065fb6954d32d427b3f7e14756f <4f5877bdf7b593e988f1924f4c3df6523f80b39c
- Affected versionversion=0b741b8234c86065fb6954d32d427b3f7e14756f <734a4d15142bb4c8ecad2d8ec70d7564e78ae34d
- Affected versionversion=0b741b8234c86065fb6954d32d427b3f7e14756f <dcafd5463d8f20c4f90ddc138a5738adb99f74c8
- Affected versionversion=4.15
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
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