System crash via unreleased socket credentials
Published Mar 10, 2021 · Updated Aug 3, 2024
Resource exhaustion in Linux Kernel before 4.5-rc3 allows local users to crash the system through interrupted UNIX socket receives. When a signal is pending, unix_stream_read_generic exits its receive loop without calling scm_destroy, leaking a struct pid reference for each interruption. Any unprivileged local account that can repeatedly interrupt UNIX-domain socket receives can consume available memory until the host crashes.
Summary
What happened
Resource exhaustion in Linux Kernel before 4.5-rc3 allows local users to crash the system through interrupted UNIX socket receives. When a signal is pending, unix_stream_read_generic exits its receive loop without calling scm_destroy, leaking a struct pid reference for each interruption. Any unprivileged local account that can repeatedly interrupt UNIX-domain socket receives can consume available memory until the host crashes.
The record
- CVE
- CVE-2021-20265
- Published
- Mar 10, 2021
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-400, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 10, 2021CVE 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=Linux kernel 4.5-rc3
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