CVE-2026-53282

Source
https://cve.org/CVERecord?id=CVE-2026-53282
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53282.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-53282
Downstream
Published
2026-06-26T19:40:43.754Z
Modified
2026-07-09T03:52:28.368511320Z
Summary
x86/kexec: Push kjump return address even for non-kjump kexec
Details

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

x86/kexec: Push kjump return address even for non-kjump kexec

The version of purgatory code shipped by kexec-tools attempts to look above the top of its stack to find a return address for a kjump, even in a non-kjump kexec.

After the commit in Fixes: the word above the stack might not be there, leading to a fault (which is at least now caught by my exception-handling code in kexec).

That commit fixed things for the actual kjump path, but no longer "gratuitously" pushes the unused return address to the stack in the non-kjump path. Put that back in the non-kjump path, to prevent purgatory from crashing when trying to access it.

Database specific
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53282.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
2cacf7f23a024ab1fdc603ca6a4f4c8b2de9f64e
Fixed
b0bd7a850e1f082560959707dbf57b0402071646
Fixed
7dba9631faa2ee0785e8c2bf0e3d90a05f26dd8c
Fixed
786a45757dcdf8f2beb9d4a6db605db16c18b2b4

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53282.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
6.14.0
Fixed
6.18.33
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.0.10

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53282.json"