Linux Kernel up to 5.18.7 time.c calibrate_ccount reference count

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Linux Kernel up to 5.18.7 and classified as critical. The impacted element is the function calibrate_ccount of the file time.c. The manipulation leads to reference count.
This vulnerability is listed as CVE-2022-49682. There is no available exploit.
The affected component should be upgraded.
Details
A vulnerability was found in Linux Kernel up to 5.18.7 and classified as critical. This issue affects the function calibrate_ccount of the file time.c. The manipulation with an unknown input leads to a reference count vulnerability. Using CWE to declare the problem leads to CWE-911. The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count. Impacted is availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: xtensa: Fix refcount leak bug in time.c In calibrate_ccount(), of_find_compatible_node() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore.
The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2022-49682 since 02/26/2025. Technical details are known, but no exploit is available.
Upgrading to version 4.9.321, 4.14.286, 4.19.250, 5.4.202, 5.10.127, 5.15.51 or 5.18.8 eliminates this vulnerability. Applying the patch 3e5eb904d9ba657308fc75a5de434b0e58dcb8d7/7de4502af68f4f3932f450157f5483eb7b33cb74/f1eaf4ba5372ad111f687a80c67e270708e14c23/e5234a9d64a976abd134a14710dcd5188158a7c5/af0ff2da01521144bc11194f4c26485d7c9cee73/0dcc1dd8a5dd9240639f1051dfaa2dffc9fbbde5/0e403a383c14b63c86bd9df085b7e573e9caee64/a0117dc956429f2ede17b323046e1968d1849150 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.320
- 4.14.285
- 4.19.249
- 5.4.201
- 5.10.126
- 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.18.0
- 5.18.1
- 5.18.2
- 5.18.3
- 5.18.4
- 5.18.5
- 5.18.6
- 5.18.7
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.7
VulDB Temp Score: 5.5
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.9.321/4.14.286/4.19.250/5.4.202/5.10.127/5.15.51/5.18.8
Patch: 3e5eb904d9ba657308fc75a5de434b0e58dcb8d7/7de4502af68f4f3932f450157f5483eb7b33cb74/f1eaf4ba5372ad111f687a80c67e270708e14c23/e5234a9d64a976abd134a14710dcd5188158a7c5/af0ff2da01521144bc11194f4c26485d7c9cee73/0dcc1dd8a5dd9240639f1051dfaa2dffc9fbbde5/0e403a383c14b63c86bd9df085b7e573e9caee64/a0117dc956429f2ede17b323046e1968d1849150
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-49682 (🔍)
GCVE (CVE): GCVE-0-2022-49682
GCVE (VulDB): GCVE-100-297293
Entry
Created: 02/26/2025 11:04Changes: 02/26/2025 11:04 (59)
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.