Linux Kernel up to 5.17.1 of_node_put reference count

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Linux Kernel up to 5.17.1. The affected element is the function of_node_put. This manipulation causes reference count.
This vulnerability appears as CVE-2022-49243. There is no available exploit.
You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Linux Kernel up to 5.17.1. Affected by this vulnerability is the function of_node_put. 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: ASoC: atmel: Add missing of_node_put() in at91sam9g20ek_audio_probe This node pointer is returned by of_parse_phandle() with refcount incremented in this function. Calling of_node_put() to avoid the refcount leak.
It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2022-49243 since 02/26/2025. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 4.9.311, 4.14.276, 4.19.238, 5.4.189, 5.10.110, 5.15.33, 5.16.19 or 5.17.2 eliminates this vulnerability. Applying the patch 81f266396237cea09a8c6322a6a78535f06ed345/f8b7b9a0594715ecfbe6f18db2328d992242654a/b0c56a0071116a37c24df998166c22a7e4684626/0325193cf40dc3a6e27d55a5b98680936deebcd0/662ee5ac6b451aa5a27b8eebd397f2f5c7f42cec/a0bc36b247dcf4d21bf820bfc4bcbaf7f6cf19b5/32e6ceb05f36432811753852c674a301f944a24b/4793a02deb31b71b3984abc67bf1011a03c13b18/f590797fa3c1bccdd19e55441592a23b46aef449 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.9.310
- 4.14.275
- 4.19.237
- 5.4.188
- 5.10.109
- 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.16.0
- 5.16.1
- 5.16.2
- 5.16.3
- 5.16.4
- 5.16.5
- 5.16.6
- 5.16.7
- 5.16.8
- 5.16.9
- 5.16.10
- 5.16.11
- 5.16.12
- 5.16.13
- 5.16.14
- 5.16.15
- 5.16.16
- 5.16.17
- 5.16.18
- 5.17.0
- 5.17.1
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.311/4.14.276/4.19.238/5.4.189/5.10.110/5.15.33/5.16.19/5.17.2
Patch: 81f266396237cea09a8c6322a6a78535f06ed345/f8b7b9a0594715ecfbe6f18db2328d992242654a/b0c56a0071116a37c24df998166c22a7e4684626/0325193cf40dc3a6e27d55a5b98680936deebcd0/662ee5ac6b451aa5a27b8eebd397f2f5c7f42cec/a0bc36b247dcf4d21bf820bfc4bcbaf7f6cf19b5/32e6ceb05f36432811753852c674a301f944a24b/4793a02deb31b71b3984abc67bf1011a03c13b18/f590797fa3c1bccdd19e55441592a23b46aef449
Timeline
02/26/2025 🔍02/26/2025 🔍
02/26/2025 🔍
10/21/2025 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2022-49243 (🔍)
GCVE (CVE): GCVE-0-2022-49243
GCVE (VulDB): GCVE-100-297523
Entry
Created: 02/26/2025 12:04Updated: 10/21/2025 18:04
Changes: 02/26/2025 12:04 (58), 10/21/2025 18:04 (11)
Complete: 🔍
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.