linux-cve-announce - CVE-2023-54146: x86/kexec: Fix double-free of elf header buffer

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025122425-CVE-2023-54146-1510@gregkh>
Date: Wed, 24 Dec 2025 14:07:43 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54146: x86/kexec: Fix double-free of elf header buffer

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

x86/kexec: Fix double-free of elf header buffer

After

  b3e34a47f989 ("x86/kexec: fix memory leak of elf header buffer"),

freeing image->elf_headers in the error path of crash_load_segments()
is not needed because kimage_file_post_load_cleanup() will take
care of that later. And not clearing it could result in a double-free.

Drop the superfluous vfree() call at the error path of
crash_load_segments().

The Linux kernel CVE team has assigned CVE-2023-54146 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.15.46 with commit 8765a423a87d74ef24ea02b43b2728fe4039f248 and fixed in 5.15.87 with commit 554a880a1fff46dd5a355dec21cd77d542a0ddf2
	Issue introduced in 5.19 with commit b3e34a47f98974d0844444c5121aaff123004e57 and fixed in 6.0.19 with commit fbdbf8ac333d3d47c0d9ea81d7d445654431d100
	Issue introduced in 5.19 with commit b3e34a47f98974d0844444c5121aaff123004e57 and fixed in 6.1.5 with commit 5bd3c7abeb69fb4133418b846a1c6dc11313d6f0
	Issue introduced in 5.19 with commit b3e34a47f98974d0844444c5121aaff123004e57 and fixed in 6.2 with commit d00dd2f2645dca04cf399d8fc692f3f69b6dd996
	Issue introduced in 5.17.14 with commit 115ee42a4c2f26ba2b4ace2668a3f004621f6833
	Issue introduced in 5.18.3 with commit f675e3a9189d84a9324ab45b0cb19906c2bc8fcb

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-2023-54146
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:
	arch/x86/kernel/crash.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/4c71a552b97fb4f46eb300224434fe56fcf4f254
	https://git.kernel.org/stable/c/554a880a1fff46dd5a355dec21cd77d542a0ddf2
	https://git.kernel.org/stable/c/fbdbf8ac333d3d47c0d9ea81d7d445654431d100
	https://git.kernel.org/stable/c/5bd3c7abeb69fb4133418b846a1c6dc11313d6f0
	https://git.kernel.org/stable/c/d00dd2f2645dca04cf399d8fc692f3f69b6dd996