CVE-2021-46968: s390/zcrypt: fix zcard and zqueue hot-unplug memleak
In the Linux kernel, the following vulnerability has been resolved:
s390/zcrypt: fix zcard and zqueue hot-unplug memleak
Tests with kvm and a kmemdebug kernel showed, that on hot unplug the
zcard and zqueue structs for the unplugged card or queue are not
properly freed because of a mismatch with get/put for the embedded
kref counter.
This fix now adjusts the handling of the kref counters. With init the
kref counter starts with 1. This initial value needs to drop to zero
with the unregister of the card or queue to trigger the release and
free the object.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects the s390 zcrypt crypto-device hot-unplug path. When a crypto card or queue is removed, kernel objects may not be freed correctly, creating a memory leak. The business risk appears narrow and availability-oriented, but the source provides no CVSS score or confirmed exploitation.
Executive priority
Handle through normal kernel patch management unless the organization operates IBM Z or s390 Linux systems with zcrypt hot-unplug workflows. For those environments, prioritize validation and patching to reduce avoidable availability risk.
Technical view
The bug is a kref get/put mismatch for embedded reference counters in zcard and zqueue structures. On hot unplug, unregister should drop the initial kref to zero so release frees the object. The kernel fix adjusts reference-count handling for cards and queues.
Likely exposure
Exposure appears limited to Linux systems using the s390/zcrypt subsystem, especially environments with crypto card or queue hot-unplug activity. Non-s390 Linux hosts are not indicated as affected by the provided sources.
Exploitation context
The provided sources do not report active exploitation, public exploit availability, or KEV listing. The described condition requires the relevant s390 zcrypt hot-unplug code path and results in leaked kernel memory objects.
Researcher notes
Evidence is limited to the CVE record and Linux stable commit references. No CVSS, CWE, exploit status, or detailed impact analysis is provided. Treat remediation mapping through distribution backports carefully rather than relying only on upstream version labels.
Mitigation direction
Update to a Linux kernel containing the referenced stable zcrypt fixes.
Prioritize s390 systems using zcrypt cards or queues.
Check Linux distribution advisories for backported fixed packages.
Minimize unnecessary zcrypt card or queue hot-unplug activity until patched.
Validation and detection
Inventory Linux hosts running on s390 architecture.
Identify systems using the zcrypt subsystem or crypto adapter queues.
Compare deployed kernel versions with vendor fixed-package guidance.
Review maintenance logs for zcrypt card or queue hot-unplug activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-46968 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.