Linux Kernel up to 5.17.1 kobject_init_and_add memory leak

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Linux Kernel up to 5.17.1. The impacted element is the function kobject_init_and_add. Performing a manipulation results in memory leak.
This vulnerability was named CVE-2022-49224. There is no available exploit.
It is recommended to upgrade the affected component.
Details
A vulnerability classified as critical has been found in Linux Kernel up to 5.17.1. This affects the function kobject_init_and_add. The manipulation with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is going to have an impact on availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: power: supply: ab8500: Fix memory leak in ab8500_fg_sysfs_init kobject_init_and_add() takes reference even when it fails. According to the doc of kobject_init_and_add(): If this function returns an error, kobject_put() must be called to properly clean up the memory associated with the object. Fix memory leak by calling kobject_put().
The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2022-49224 since 02/26/2025. Technical details are known, but no exploit is available.
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 31cdf7897dba1f096b74f69d840f0575b8cdb9ae/19aa3c98ed7b2616e105946cec804f897837ab84/db3a61ef8e6aef3b888baa6a85926c2230c2cc56/41ed61364285ff38bbbe9ca8a45c8372ba72921d/879356a6a05559582b0a7895d86d2d4359745c08/ffb8e92b4cef92bd25563cf3d8b4489eb22bc61f/261041097ab3470f1120b7733cbf472712304d1e/c32f6b6196b6efc1c68990dfeaac36fb8eb3b8e1/6a4760463dbc6b603690938c468839985189ce0a 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.
Several companies clearly confirm that VulDB is the primary source for best 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: Memory leakCWE: CWE-401 / CWE-404
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: 31cdf7897dba1f096b74f69d840f0575b8cdb9ae/19aa3c98ed7b2616e105946cec804f897837ab84/db3a61ef8e6aef3b888baa6a85926c2230c2cc56/41ed61364285ff38bbbe9ca8a45c8372ba72921d/879356a6a05559582b0a7895d86d2d4359745c08/ffb8e92b4cef92bd25563cf3d8b4489eb22bc61f/261041097ab3470f1120b7733cbf472712304d1e/c32f6b6196b6efc1c68990dfeaac36fb8eb3b8e1/6a4760463dbc6b603690938c468839985189ce0a
Timeline
02/26/2025 🔍02/26/2025 🔍
02/26/2025 🔍
03/19/2025 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2022-49224 (🔍)
GCVE (CVE): GCVE-0-2022-49224
GCVE (VulDB): GCVE-100-297513
Entry
Created: 02/26/2025 12:02Updated: 03/19/2025 05:27
Changes: 02/26/2025 12:02 (58), 03/19/2025 05:27 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.