x86/kexec: Push kjump return address even for non-kjump kexec
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 786a45757dcdf8f2beb9d4a6db605db16c18b2b4, Kernel 7dba9631faa2ee0785e8c2bf0e3d90a05f26dd8c and Kernel b0bd7a850e1f082560959707dbf57b0402071646.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.14, >=2cacf7f23a024ab1fdc603ca6a4f4c8b2de9f64e <786a45757dcdf8f2beb9d4a6db605db16c18b2b4, >=2cacf7f23a024ab1fdc603ca6a4f4c8b2de9f64e <7dba9631faa2ee0785e8c2bf0e3d90a05f26dd8c, >=2cacf7f23a024ab1fdc603ca6a4f4c8b2de9f64e <b0bd7a850e1f082560959707dbf57b0402071646 | 786a45757dcdf8f2beb9d4a6db605db16c18b2b4, 7dba9631faa2ee0785e8c2bf0e3d90a05f26dd8c, b0bd7a850e1f082560959707dbf57b0402071646 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket