KVM: SVM: Use kzalloc for sev ioctl interfaces to prevent kernel data leak

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1003179: KVM: SVM: Use kzalloc for sev ioctl interfaces to prevent kernel data leak. Affects Kernel versions >= eaf78265a4ab33935d3a0f1407ce4a91aac4d4d5, < bbdcc644b59e01e98c68894a9fab42b9687f42b0. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Kernel package is a fundamental component of the Linux operating system. It provides the core functionality and interfaces for the system's hardware, software, and user applications. The Kernel package is responsible for managing system resources, handling device drivers, and facilitating communication between different components of the operating system. This vulnerability specifically affects the Kernel package's SVM (Secure Virtual Machine) module, which is responsible for providing hardware-assisted virtualization capabilities on AMD processors.

Vulnerability Detail

The vulnerability in the SVM module of the Kernel package allows for a kernel data leak. By exploiting this vulnerability, an attacker could potentially access sensitive information from the kernel memory, leading to unauthorized disclosure of data and potential privilege escalation. The vulnerability was introduced in version v5.7 of the Linux Kernel and was fixed in version v5.17.13. The fix involves using kzalloc instead of kmalloc for sev ioctl interfaces, which ensures that the allocated memory is zeroed out, preventing any potential data leaks.

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 solution is to apply the fix by updating the Linux Kernel package.

Conclusion

The vulnerability in the SVM module of the Kernel package could allow for a kernel data leak, potentially leading to unauthorized disclosure of data and privilege escalation. It is crucial to update the Linux Kernel package to version v5.17.13 or later to mitigate this vulnerability. Users can also utilize the Vulert Playground (https://vulert.com/scanner) to check if their system is affected by this vulnerability. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability could allow an attacker to access sensitive information from the kernel memory, potentially leading to unauthorized disclosure of data and privilege escalation.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert Playground will analyze it for any known vulnerabilities, including this one.

At the time of this report, there are no known exploits for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.

No, this vulnerability requires local access to the system in order to exploit it.

For further support on vulnerability remediation, you can contact info@devnack.com. They can provide guidance and assistance in fixing this vulnerability.

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