Linux Kernel up to 5.10.153/5.15.77/6.0.7 tracing kretprobe_cmd memory leak

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.6$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Linux Kernel up to 5.10.153/5.15.77/6.0.7. This vulnerability affects the function kretprobe_cmd of the component tracing. This manipulation causes memory leak. This vulnerability is tracked as CVE-2022-49891. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 5.10.153/5.15.77/6.0.7 and classified as critical. Affected by this vulnerability is the function kretprobe_cmd of the component tracing. The manipulation with an unknown input leads to a memory leak vulnerability. The CWE definition for the vulnerability is CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. As an impact it is known to affect availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: tracing: kprobe: Fix memory leak in test_gen_kprobe/kretprobe_cmd() test_gen_kprobe_cmd() only free buf in fail path, hence buf will leak when there is no failure. Move kfree(buf) from fail path to common path to prevent the memleak. The same reason and solution in test_gen_kretprobe_cmd(). unreferenced object 0xffff888143b14000 (size 2048): comm "insmod", pid 52490, jiffies 4301890980 (age 40.553s) hex dump (first 32 bytes): 70 3a 6b 70 72 6f 62 65 73 2f 67 65 6e 5f 6b 70 p:kprobes/gen_kp 72 6f 62 65 5f 74 65 73 74 20 64 6f 5f 73 79 73 robe_test do_sys backtrace: [] kmalloc_trace+0x27/0xa0 [] 0xffffffffa059006f [] do_one_initcall+0x87/0x2a0 [] do_init_module+0xdf/0x320 [] load_module+0x3006/0x3390 [] __do_sys_finit_module+0x113/0x1b0 [] do_syscall_64+0x35/0x80 [] entry_SYSCALL_64_after_hwframe+0x46/0xb0

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2022-49891 since 05/01/2025. The exploitation appears to be difficult. Technical details are known, but no exploit is available.

Upgrading to version 5.10.154, 5.15.78 or 6.0.8 eliminates this vulnerability. Applying the patch bef08acbe560a926b4cee9cc46404cc98ae5703b/d1b6a8e3414aeaa0985139180c145d2d0fbd2a49/71aeb8d01a8c7ab5cf7da3f81b35206f56ce6bca/66f0919c953ef7b55e5ab94389a013da2ce80a2c 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.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.8
VulDB Meta Temp Score: 4.6

VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Kernel 5.10.154/5.15.78/6.0.8
Patch: bef08acbe560a926b4cee9cc46404cc98ae5703b/d1b6a8e3414aeaa0985139180c145d2d0fbd2a49/71aeb8d01a8c7ab5cf7da3f81b35206f56ce6bca/66f0919c953ef7b55e5ab94389a013da2ce80a2c

Timelineinfo

05/01/2025 🔍
05/01/2025 +0 days 🔍
05/01/2025 +0 days 🔍
05/01/2025 +0 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-49891 (🔍)
GCVE (CVE): GCVE-0-2022-49891
GCVE (VulDB): GCVE-100-307057

Entryinfo

Created: 05/01/2025 19:03
Changes: 05/01/2025 19:03 (59)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Might our Artificial Intelligence support you?

Check our Alexa App!