Memory Leak Vulnerability in x86/kexec

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1002849: x86/kexec: fix memory leak of elf header buffer. Affects Kernel versions < f675e3a9189d84a9324ab45b0cb19906c2bc8fcb. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The x86/kexec is a component of the Linux Kernel that allows for the loading and booting of a new kernel from the currently running kernel. It is commonly used for system recovery or kernel debugging purposes. The vulnerability identified in this component involves a memory leak issue related to the handling of ELF headers. An attacker could potentially exploit this vulnerability to exhaust system memory resources, leading to a denial of service condition or other security implications.

Vulnerability Detail

The vulnerability in x86/kexec arises from a memory leak in the handling of ELF headers. When loading a new kernel, the component allocates memory to store the ELF header information. However, in certain scenarios, this memory is not properly deallocated, resulting in a memory leak. An attacker could repeatedly trigger the loading of new kernels, causing the system to gradually run out of memory resources. This could lead to system instability, crashes, or even potential privilege escalation if the attacker can control the content of the loaded kernels.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended approach is to apply the kernel update as mentioned in the 'how_to_fix' section.

Conclusion

The memory leak vulnerability in x86/kexec can have serious implications on system stability and security. It is crucial to update the Linux Kernel to version v5.18.3 or later to address this vulnerability. Failure to do so may result in resource exhaustion and potential privilege escalation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

x86/kexec is a component of the Linux Kernel that allows for the loading and booting of a new kernel from the currently running kernel. It is commonly used for system recovery or kernel debugging purposes.

The vulnerability could lead to a memory leak, causing the system to gradually run out of memory resources. This can result in system instability, crashes, or potential privilege escalation if the attacker can control the content of the loaded kernels.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.18.3 or later. This fix is implemented in commit f675e3a9189d84a9324ab45b0cb19906c2bc8fcb.

There is no specific workaround mentioned for this vulnerability. The recommended approach is to apply the kernel update as mentioned in the 'how_to_fix' section.

The vulnerability itself does not specify whether it can be exploited remotely or requires local access. However, as it involves the Linux Kernel, it is advisable to keep the kernel updated to mitigate potential security risks.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback