Linux Kernel up to 5.18.10 meson_smp_prepare_cpus of_find_compatible_node reference count

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Linux Kernel up to 4.19.251/5.4.204/5.10.129/5.15.53/5.18.10. The affected element is the function of_find_compatible_node of the component meson_smp_prepare_cpus. This manipulation causes reference count.
The identification of this vulnerability is CVE-2022-49656. There is no exploit available.
It is suggested to upgrade the affected component.
Details
A vulnerability was found in Linux Kernel up to 4.19.251/5.4.204/5.10.129/5.15.53/5.18.10. It has been declared as problematic. Affected by this vulnerability is the function of_find_compatible_node of the component meson_smp_prepare_cpus. The manipulation with an unknown input leads to a reference count vulnerability. The CWE definition for the vulnerability is CWE-911. The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count. As an impact it is known to affect availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: ARM: meson: Fix refcount leak in meson_smp_prepare_cpus of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak.
It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2022-49656 since 02/26/2025. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 4.19.252, 5.4.205, 5.10.130, 5.15.54 or 5.18.11 eliminates this vulnerability. Applying the patch 2e1bcd33478ef44e63a45457055060b5fe4118ad/3cf8ece9113242c10f83c7675ea4f4f67959ee43/3d90607e7e6afa89768b0aaa915b58bd2b849276/7208101ded1e9dcc52c8f0f8b16474211c871c1a/c5fbf4f74c94fd60d5e9bf9f7f8268c3601562ca/34d2cd3fccced12b958b8848e3eff0ee4296764c is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 4.19.251
- 5.4.204
- 5.10.129
- 5.15.0
- 5.15.1
- 5.15.2
- 5.15.3
- 5.15.4
- 5.15.5
- 5.15.6
- 5.15.7
- 5.15.8
- 5.15.9
- 5.15.10
- 5.15.11
- 5.15.12
- 5.15.13
- 5.15.14
- 5.15.15
- 5.15.16
- 5.15.17
- 5.15.18
- 5.15.19
- 5.15.20
- 5.15.21
- 5.15.22
- 5.15.23
- 5.15.24
- 5.15.25
- 5.15.26
- 5.15.27
- 5.15.28
- 5.15.29
- 5.15.30
- 5.15.31
- 5.15.32
- 5.15.33
- 5.15.34
- 5.15.35
- 5.15.36
- 5.15.37
- 5.15.38
- 5.15.39
- 5.15.40
- 5.15.41
- 5.15.42
- 5.15.43
- 5.15.44
- 5.15.45
- 5.15.46
- 5.15.47
- 5.15.48
- 5.15.49
- 5.15.50
- 5.15.51
- 5.15.52
- 5.15.53
- 5.18.0
- 5.18.1
- 5.18.2
- 5.18.3
- 5.18.4
- 5.18.5
- 5.18.6
- 5.18.7
- 5.18.8
- 5.18.9
- 5.18.10
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Reference countCWE: CWE-911 / CWE-664
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kernel 4.19.252/5.4.205/5.10.130/5.15.54/5.18.11
Patch: 2e1bcd33478ef44e63a45457055060b5fe4118ad/3cf8ece9113242c10f83c7675ea4f4f67959ee43/3d90607e7e6afa89768b0aaa915b58bd2b849276/7208101ded1e9dcc52c8f0f8b16474211c871c1a/c5fbf4f74c94fd60d5e9bf9f7f8268c3601562ca/34d2cd3fccced12b958b8848e3eff0ee4296764c
Timeline
02/26/2025 🔍02/26/2025 🔍
02/26/2025 🔍
02/26/2025 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2022-49656 (🔍)
GCVE (CVE): GCVE-0-2022-49656
GCVE (VulDB): GCVE-100-297259
Entry
Created: 02/26/2025 10:57Changes: 02/26/2025 10:57 (59)
Complete: 🔍
Committer: sany
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.