Local service interruption via AES-GCM resource leaks
Published Aug 23, 2022 · Updated Aug 3, 2024
Memory leaks in Linux Kernel before 5.15-rc4 allow local users to exhaust memory and interrupt service through AES-GCM operations. In ccp_run_aes_gcm_cmd() in drivers/crypto/ccp/ccp-ops.c, three error paths skip freeing aad, final_wa, or tag allocations after initialization or AES operation failures. Low-privileged local access is required, and repeated triggering consumes kernel memory until system availability is impaired.
Summary
What happened
Memory leaks in Linux Kernel before 5.15-rc4 allow local users to exhaust memory and interrupt service through AES-GCM operations. In ccp_run_aes_gcm_cmd() in drivers/crypto/ccp/ccp-ops.c, three error paths skip freeing aad, final_wa, or tag allocations after initialization or AES operation failures. Low-privileged local access is required, and repeated triggering consumes kernel memory until system availability is impaired.
The record
- CVE
- CVE-2021-3764
- Published
- Aug 23, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-400, CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 23, 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
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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