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

Medium 5.5 Published Updated

A missing stack push in the Linux kernel kexec path causes a fault when purgatory accesses a non-existent return address, leading to a crash.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-53282?

CVE-2026-53282 is a medium-severity vulnerability in Linux kernel, published on 26 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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.

Which versions are affected by CVE-2026-53282?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2026-53282?

Apply the vendor's patch.

Is CVE-2026-53282 being exploited?

There is no known exploitation of CVE-2026-53282 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as BELL-CVE-2026-53282, DEBIAN-CVE-2026-53282, GHSA-865v-r97p-c9pq, UBUNTU-CVE-2026-53282.

Is CVE-2026-53282 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free