| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025022652-CVE-2022-49410-de6a@gregkh> Date: Wed, 26 Feb 2025 03:11:24 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2022-49410: tracing: Fix potential double free in create_var_ref() Description =========== In the Linux kernel, the following vulnerability has been resolved: tracing: Fix potential double free in create_var_ref() In create_var_ref(), init_var_ref() is called to initialize the fields of variable ref_field, which is allocated in the previous function call to create_hist_field(). Function init_var_ref() allocates the corresponding fields such as ref_field->system, but frees these fields when the function encounters an error. The caller later calls destroy_hist_field() to conduct error handling, which frees the fields and the variable itself. This results in double free of the fields which are already freed in the previous function. Fix this by storing NULL to the corresponding fields when they are freed in init_var_ref(). The Linux kernel CVE team has assigned CVE-2022-49410 to this issue. Affected and fixed versions =========================== Issue introduced in 4.17 with commit 067fe038e70f6e64960d26a79c4df5f1413d0f13 and fixed in 4.19.247 with commit f8b383f83cb573152c577eca1ef101e89995b72a Issue introduced in 4.17 with commit 067fe038e70f6e64960d26a79c4df5f1413d0f13 and fixed in 5.4.198 with commit c27f744ceefadc7bbeb14233b6abc150ced617d2 Issue introduced in 4.17 with commit 067fe038e70f6e64960d26a79c4df5f1413d0f13 and fixed in 5.10.121 with commit 058cb6d86b9789377216c936506b346aaa1eb581 Issue introduced in 4.17 with commit 067fe038e70f6e64960d26a79c4df5f1413d0f13 and fixed in 5.15.46 with commit 37443b3508b8cce6832f8d25cb4550b2f7801f50 Issue introduced in 4.17 with commit 067fe038e70f6e64960d26a79c4df5f1413d0f13 and fixed in 5.17.14 with commit 4fdfb15e08598711dbf50daf56a33965232daf0e Issue introduced in 4.17 with commit 067fe038e70f6e64960d26a79c4df5f1413d0f13 and fixed in 5.18.3 with commit bd83ff3bbfb003832481c9bff999d12385f396ae Issue introduced in 4.17 with commit 067fe038e70f6e64960d26a79c4df5f1413d0f13 and fixed in 5.19 with commit 99696a2592bca641eb88cc9a80c90e591afebd0f Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2022-49410 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: kernel/trace/trace_events_hist.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/f8b383f83cb573152c577eca1ef101e89995b72a https://git.kernel.org/stable/c/c27f744ceefadc7bbeb14233b6abc150ced617d2 https://git.kernel.org/stable/c/058cb6d86b9789377216c936506b346aaa1eb581 https://git.kernel.org/stable/c/37443b3508b8cce6832f8d25cb4550b2f7801f50 https://git.kernel.org/stable/c/4fdfb15e08598711dbf50daf56a33965232daf0e https://git.kernel.org/stable/c/bd83ff3bbfb003832481c9bff999d12385f396ae https://git.kernel.org/stable/c/99696a2592bca641eb88cc9a80c90e591afebd0f
Powered by blists - more mailing lists