CVE-2022-49678: soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 10ba9d499a9fd82ed40897e734ba19870a879407, 30bbfeb480ae8b5ee43199d72417b232590440c2, 37d838de369b07b596c19ff3662bf0293fdb09ee.
Low priority for now. Upgrade to Linux Linux 10ba9d499a9fd82ed40897e734ba19870a879407, 30bbfeb480ae8b5ee43199d72417b232590440c2, 37d838de369b07b596c19ff3662bf0293fdb09ee or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe of_find_matching_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak. In brcmstb_init_sram, it pass dn to of_address_to_resource(), of_address_to_resource() will call of_find_device_by_node() to take reference, so we should release the reference returned by of_find_matching_node().
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.15 and later · before 4.19.250
- linux linux kernel4.20 and later · before 5.4.202
- linux linux kernel5.5 and later · before 5.10.127
- linux linux kernel5.11 and later · before 5.15.51
- linux linux kernel5.16 and later · before 5.18.8
- linux linux kernel5.19
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.15affected
- 0b741b8234c86065fb6954d32d427b3f7e14756f and later · before 4f5877bdf7b593e988f1924f4c3df6523f80b39caffected · git
- 0b741b8234c86065fb6954d32d427b3f7e14756f and later · before 734a4d15142bb4c8ecad2d8ec70d7564e78ae34daffected · git
- 0b741b8234c86065fb6954d32d427b3f7e14756f and later · before 30bbfeb480ae8b5ee43199d72417b232590440c2affected · git
- 0b741b8234c86065fb6954d32d427b3f7e14756f and later · before 10ba9d499a9fd82ed40897e734ba19870a879407affected · git
- 0b741b8234c86065fb6954d32d427b3f7e14756f and later · before dcafd5463d8f20c4f90ddc138a5738adb99f74c8affected · git
- 0b741b8234c86065fb6954d32d427b3f7e14756f and later · before 37d838de369b07b596c19ff3662bf0293fdb09eeaffected · git
- before 4.15not affected · semver
- 4.19.250 and later · up to and including 4.19.*not affected · semver
- 5.4.202 and later · up to and including 5.4.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.18.14-1 | 5.18.14-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49676Feb 26, 2025 · memory: samsung: exynos5422-dmc: Fix refcount leak in of_get_dram_timings22Monitor
- ← EarlierCVE-2022-49677Feb 26, 2025 · ARM: cns3xxx: Fix refcount leak in cns3xxx_init22Monitor
- Later →CVE-2022-49679Feb 26, 2025 · ARM: Fix refcount leak in axxia_boot_secondary22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 10ba9d499a9fd82ed40897e734ba19870a879407 | Vendor (CNA) |
| Linux Linux | 30bbfeb480ae8b5ee43199d72417b232590440c2 | Vendor (CNA) |
| Linux Linux | 37d838de369b07b596c19ff3662bf0293fdb09ee | Vendor (CNA) |
| Linux Linux | 4f5877bdf7b593e988f1924f4c3df6523f80b39c | Vendor (CNA) |
| Linux Linux | 734a4d15142bb4c8ecad2d8ec70d7564e78ae34d | Vendor (CNA) |
| Linux Linux | dcafd5463d8f20c4f90ddc138a5738adb99f74c8 | Vendor (CNA) |
| debian:linux | 5.18.14-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/30bbfeb480ae8b5ee43199d72417b232590440c2
- git.kernel.org/stable/c/37d838de369b07b596c19ff3662bf0293fdb09ee
- git.kernel.org/stable/c/4f5877bdf7b593e988f1924f4c3df6523f80b39c
- git.kernel.org/stable/c/734a4d15142bb4c8ecad2d8ec70d7564e78ae34d
- git.kernel.org/stable/c/dcafd5463d8f20c4f90ddc138a5738adb99f74c8
Vendor advisories and official records. Exploit/PoC links are deliberately left out.