Local denial of service via AES-GCM memory leaks
Published Mar 4, 2022 · Updated Aug 3, 2024
Memory leaks in Linux Kernel before 5.15-rc4 allow local users to exhaust kernel memory and interrupt service through AES-GCM requests. In ccp_run_aes_gcm_cmd() in drivers/crypto/ccp/ccp-ops.c, three failure paths omit freeing the aad, final_wa, or tag allocation. A local low-privilege user must reach the AMD v5 Crypto Co-Processor AES-GCM path and repeatedly induce its allocation failures, causing availability loss through memory exhaustion.
Summary
What happened
Memory leaks in Linux Kernel before 5.15-rc4 allow local users to exhaust kernel memory and interrupt service through AES-GCM requests. In ccp_run_aes_gcm_cmd() in drivers/crypto/ccp/ccp-ops.c, three failure paths omit freeing the aad, final_wa, or tag allocation. A local low-privilege user must reach the AMD v5 Crypto Co-Processor AES-GCM path and repeatedly induce its allocation failures, causing availability loss through memory exhaustion.
The record
- CVE
- CVE-2021-3744
- Published
- Mar 4, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 4, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed in v5.15-rc4 and above.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo