Linux Kernel up to 5.18.5 of_find_matching_node_and_match reference count

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 5.18.5. It has been classified as critical. Affected by this issue is the function of_find_matching_node_and_match. Performing a manipulation results in reference count.
This vulnerability is cataloged as CVE-2022-49719. There is no exploit available.
Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, was found in Linux Kernel up to 5.18.5. This affects the function of_find_matching_node_and_match. The manipulation with an unknown input leads to a reference count vulnerability. CWE is classifying the issue as CWE-911. The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count. This is going to have an impact on availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: irqchip/gic/realview: Fix refcount leak in realview_gic_of_init of_find_matching_node_and_match() 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.
The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2022-49719 since 02/26/2025. Technical details are known, but no exploit is available.
Upgrading to version 4.9.320, 4.14.285, 4.19.249, 5.4.200, 5.10.124, 5.15.49 or 5.18.6 eliminates this vulnerability. Applying the patch 87da903ce632d5689bef66d56ee5dae700d82104/486f68f85085d9b16ae097679b1486dcb1b6eb69/b634af84bc1edece4e63317b0ad95618dd3a8693/56526c3883fc7a1f5898b1d40a02c8b8685a5d92/e52a58b79f11755ea7e877015c4a1704303fa55f/5d38720661a4b9c87705c206a6081177ffb8ec1d/16b603cb8d34c2d917983918db1f88c8b831baaa/f4b98e314888cc51486421bcf6d52852452ea48b 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 4.9.319
- 4.14.284
- 4.19.248
- 5.4.199
- 5.10.123
- 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.18.0
- 5.18.1
- 5.18.2
- 5.18.3
- 5.18.4
- 5.18.5
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
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: Partially
Local: Yes
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.9.320/4.14.285/4.19.249/5.4.200/5.10.124/5.15.49/5.18.6
Patch: 87da903ce632d5689bef66d56ee5dae700d82104/486f68f85085d9b16ae097679b1486dcb1b6eb69/b634af84bc1edece4e63317b0ad95618dd3a8693/56526c3883fc7a1f5898b1d40a02c8b8685a5d92/e52a58b79f11755ea7e877015c4a1704303fa55f/5d38720661a4b9c87705c206a6081177ffb8ec1d/16b603cb8d34c2d917983918db1f88c8b831baaa/f4b98e314888cc51486421bcf6d52852452ea48b
Timeline
02/26/2025 🔍02/26/2025 🔍
02/26/2025 🔍
03/08/2025 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2022-49719 (🔍)
GCVE (CVE): GCVE-0-2022-49719
GCVE (VulDB): GCVE-100-297309
Entry
Created: 02/26/2025 11:08Updated: 03/08/2025 09:08
Changes: 02/26/2025 11:08 (58), 03/08/2025 09:08 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.