From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43289: kexec: derive purgatory entry from symbol
Date: Fri, 8 May 2026 15:11:54 +0200 [thread overview]
Message-ID: <2026050852-CVE-2026-43289-ad06@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
kexec: derive purgatory entry from symbol
kexec_load_purgatory() derives image->start by locating e_entry inside an
SHF_EXECINSTR section. If the purgatory object contains multiple
executable sections with overlapping sh_addr, the entrypoint check can
match more than once and trigger a WARN.
Derive the entry section from the purgatory_start symbol when present and
compute image->start from its final placement. Keep the existing e_entry
fallback for purgatories that do not expose the symbol.
WARNING: kernel/kexec_file.c:1009 at kexec_load_purgatory+0x395/0x3c0, CPU#10: kexec/1784
Call Trace:
<TASK>
bzImage64_load+0x133/0xa00
__do_sys_kexec_file_load+0x2b3/0x5c0
do_syscall_64+0x81/0x610
entry_SYSCALL_64_after_hwframe+0x76/0x7e
[me@linux.beauty: move helper to avoid forward declaration, per Baoquan]
The Linux kernel CVE team has assigned CVE-2026-43289 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.10.185 with commit f368aed4827bd4276c0e3664fb2cb815a8d7caf3 and fixed in 5.10.252 with commit 027797595a108726f4a0a45d225f603b0ffbd22b
Issue introduced in 5.15.118 with commit d38e051ec6fd8650b139d9bc4b0b8b261953b263 and fixed in 5.15.202 with commit 1737d37ae1d2814e6cf0a1af87af3d41f0812b95
Issue introduced in 6.1.35 with commit 013027918a4efa807409fcb356009c117e4d181a and fixed in 6.1.165 with commit f736032c638a33a243e9126e617788f763d648f9
Issue introduced in 6.4 with commit 8652d44f466ad5772e7d1756e9457046189b0dfc and fixed in 6.6.128 with commit cfccd3b8c51bc57a8a6fcb2fd30453afae5bc0d2
Issue introduced in 6.4 with commit 8652d44f466ad5772e7d1756e9457046189b0dfc and fixed in 6.12.75 with commit 875355152b33436907c2a6d2ffad1431fa86c62b
Issue introduced in 6.4 with commit 8652d44f466ad5772e7d1756e9457046189b0dfc and fixed in 6.18.16 with commit 36eb314184a0ae74dd42914b47d2b9fc43be8034
Issue introduced in 6.4 with commit 8652d44f466ad5772e7d1756e9457046189b0dfc and fixed in 6.19.6 with commit 5226570bd252cea2e805a161cb0f75c204c3108a
Issue introduced in 6.4 with commit 8652d44f466ad5772e7d1756e9457046189b0dfc and fixed in 7.0 with commit 480e1d5c64bb14441f79f2eb9421d5e26f91ea3d
Issue introduced in 4.19.287 with commit 4947a0eb7d642b6048559857964966016ef3aa8b
Issue introduced in 5.4.248 with commit b16bf76b382810257e3fb6278663a9d131b70197
Issue introduced in 6.3.9 with commit cb1638618545182a01444b2b20a4ed6b9d2a8c8f
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-2026-43289
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/kexec_file.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/027797595a108726f4a0a45d225f603b0ffbd22b
https://git.kernel.org/stable/c/1737d37ae1d2814e6cf0a1af87af3d41f0812b95
https://git.kernel.org/stable/c/f736032c638a33a243e9126e617788f763d648f9
https://git.kernel.org/stable/c/cfccd3b8c51bc57a8a6fcb2fd30453afae5bc0d2
https://git.kernel.org/stable/c/875355152b33436907c2a6d2ffad1431fa86c62b
https://git.kernel.org/stable/c/36eb314184a0ae74dd42914b47d2b9fc43be8034
https://git.kernel.org/stable/c/5226570bd252cea2e805a161cb0f75c204c3108a
https://git.kernel.org/stable/c/480e1d5c64bb14441f79f2eb9421d5e26f91ea3d
reply other threads:[~2026-05-08 13:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026050852-CVE-2026-43289-ad06@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox