CVE-2022-49837

  1. OpenCVE
  2. Vulnerabilities (CVE)
  3. CVE-2022-49837
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix memory leaks in __check_func_call kmemleak reports this issue: unreferenced object 0xffff88817139d000 (size 2048): comm "test_progs", pid 33246, jiffies 4307381979 (age 45851.820s) hex dump (first 32 bytes): 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<0000000045f075f0>] kmalloc_trace+0x27/0xa0 [<0000000098b7c90a>] __check_func_call+0x316/0x1230 [<00000000b4c3c403>] check_helper_call+0x172e/0x4700 [<00000000aa3875b7>] do_check+0x21d8/0x45e0 [<000000001147357b>] do_check_common+0x767/0xaf0 [<00000000b5a595b4>] bpf_check+0x43e3/0x5bc0 [<0000000011e391b1>] bpf_prog_load+0xf26/0x1940 [<0000000007f765c0>] __sys_bpf+0xd2c/0x3650 [<00000000839815d6>] __x64_sys_bpf+0x75/0xc0 [<00000000946ee250>] do_syscall_64+0x3b/0x90 [<0000000000506b7f>] entry_SYSCALL_64_after_hwframe+0x63/0xcd The root case here is: In function prepare_func_exit(), the callee is not released in the abnormal scenario after "state->curframe--;". To fix, move "state->curframe--;" to the very bottom of the function, right when we free callee and reset frame[] pointer to NULL, as Andrii suggested. In addition, function __check_func_call() has a similar problem. In the abnormal scenario before "state->curframe++;", the callee also should be released by free_func_state().

5.5 /10

CVSS v3 : MEDIUM

V3 Legend

Vector :

Exploitability : 1.8 / Impact : 3.6

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

References
Link Resource
https://git.kernel.org/stable/c/83946d772e756734a900ef99dbe0aeda506adf37 Patch
https://git.kernel.org/stable/c/d4944497827a3d14bc5a26dbcfb7433eb5a956c0 Patch
https://git.kernel.org/stable/c/eb86559a691cea5fa63e57a03ec3dc9c31e97955 Patch
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc5:*:*:*:*:*:*
History

07 May 2025, 13:33

Type Values Removed Values Added
CWE CWE-401
References () https://git.kernel.org/stable/c/83946d772e756734a900ef99dbe0aeda506adf37 - () https://git.kernel.org/stable/c/83946d772e756734a900ef99dbe0aeda506adf37 - Patch
References () https://git.kernel.org/stable/c/d4944497827a3d14bc5a26dbcfb7433eb5a956c0 - () https://git.kernel.org/stable/c/d4944497827a3d14bc5a26dbcfb7433eb5a956c0 - Patch
References () https://git.kernel.org/stable/c/eb86559a691cea5fa63e57a03ec3dc9c31e97955 - () https://git.kernel.org/stable/c/eb86559a691cea5fa63e57a03ec3dc9c31e97955 - Patch
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 5.5
First Time Linux linux Kernel
Linux
CPE cpe:2.3:o:linux:linux_kernel:6.1:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc3:*:*:*:*:*:*

02 May 2025, 13:53

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: bpf: Se corrigen fugas de memoria en __check_func_call kmemleak informa de este problema: objeto sin referencia 0xffff88817139d000 (tamaño 2048): comm "test_progs", pid 33246, jiffies 4307381979 (edad 45851.820s) volcado hexadecimal (primeros 32 bytes): 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [&lt;0000000045f075f0&gt;] kmalloc_trace+0x27/0xa0 [&lt;0000000098b7c90a&gt;] __check_func_call+0x316/0x1230 [&lt;00000000b4c3c403&gt;] check_helper_call+0x172e/0x4700 [&lt;00000000aa3875b7&gt;] do_check+0x21d8/0x45e0 [&lt;000000001147357b&gt;] do_check_common+0x767/0xaf0 [&lt;00000000b5a595b4&gt;] bpf_check+0x43e3/0x5bc0 [&lt;0000000011e391b1&gt;] bpf_prog_load+0xf26/0x1940 [&lt;0000000007f765c0&gt;] __sys_bpf+0xd2c/0x3650 [&lt;00000000839815d6&gt;] __x64_sys_bpf+0x75/0xc0 [&lt;00000000946ee250&gt;] do_syscall_64+0x3b/0x90 [&lt;0000000000506b7f&gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd El caso raíz aquí es: En la función prepare_func_exit(), el llamado no se libera en el escenario anormal después de "state-&gt;curframe--;". Para solucionarlo, mueva "state-&gt;curframe--;" al final de la función, justo cuando liberamos al destinatario y restablecemos el puntero frame[] a NULL, como sugirió Andrii. Además, la función __check_func_call() presenta un problema similar. En el escenario anormal anterior a "state-&gt;curframe++;", el destinatario también debería ser liberado por free_func_state().

01 May 2025, 15:16

Type Values Removed Values Added
New CVE
Information

Published : 2025-05-01 15:16

Updated : 2025-05-07 13:33

NVD link : CVE-2022-49837

Mitre link : CVE-2022-49837

CVE.ORG link : CVE-2022-49837

JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-401

Missing Release of Memory after Effective Lifetime