Vulnerability in s390/zcrypt: Fix zcard and zqueue Hot-Unplug Memory Leak

Kernel Updated 02 Oct 2025

Summary

31/05/2021
N/A
No i
Unrated
Not published

GSD-2021-1000160: s390/zcrypt: fix zcard and zqueue hot-unplug memleak. Affects Kernel versions >= 29c2680fd2bf3862ff5cf2957f198512493156f9, < 026499a9c2e002e621ad568d1378324ae97e5524. 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 s390/zcrypt package is a component of the Linux Kernel that provides cryptographic support for IBM System z hardware. It includes drivers and interfaces for managing cryptographic cards (zcards) and cryptographic queues (zqueues). These components are responsible for offloading cryptographic operations to dedicated hardware, improving performance and security. However, a vulnerability has been discovered in the hot-unplug process of zcards and zqueues, leading to a memory leak.

Vulnerability Detail

The vulnerability in s390/zcrypt affects the hot-unplug functionality of zcards and zqueues. When a zcard or zqueue is hot-unplugged, a memory leak occurs, resulting in the consumption of system resources. This can lead to performance degradation and potential denial-of-service conditions. The vulnerability was introduced in Linux Kernel version v5.10 by commit 29c2680fd2bf3862ff5cf2957f198512493156f9 and has been fixed in version v5.10.36 by commit 026499a9c2e002e621ad568d1378324ae97e5524.

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 known workaround for this vulnerability. It is necessary to apply the fix by updating the Linux Kernel.

Conclusion

The vulnerability in s390/zcrypt's hot-unplug process for zcards and zqueues can lead to a memory leak, causing performance degradation and potential denial-of-service conditions. It is crucial to update the Linux Kernel to version v5.10.36 or later to mitigate this vulnerability. For further assistance, please reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can result in a memory leak, leading to performance degradation and potential denial-of-service conditions.

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 Vulert will analyze it for any open-source vulnerabilities, including this one.

No, this vulnerability requires local access to the system in order to hot-unplug zcards or zqueues.

There are no known instances of this vulnerability being exploited in the wild.

For further support on vulnerability remediation, you can contact info@devnack.com.

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