Local crash via excessive stack allocation
Published Jul 20, 2021 · Updated Jun 9, 2025
Memory allocation flaw in systemd before 246.15, 247.8, 248.5, and 249.1 allows local users to crash the operating system. The basic/unit-name.c path handling uses strdupa and alloca on an attacker-controlled pathname, exhausting the stack while constructing a unit name. Local users able to provide a sufficiently long pathname can trigger a systemd or PID 1 crash, producing an availability-only service interruption.
Summary
What happened
Memory allocation flaw in systemd before 246.15, 247.8, 248.5, and 249.1 allows local users to crash the operating system. The basic/unit-name.c path handling uses strdupa and alloca on an attacker-controlled pathname, exhausting the stack while constructing a unit name. Local users able to provide a sufficiently long pathname can trigger a systemd or PID 1 crash, producing an availability-only service interruption.
The record
- CVE
- CVE-2021-33910
- Published
- Jul 20, 2021
- Updated
- Jun 9, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-770, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 20, 2021CVE publishedPublication date reported by the CVE source.
- Jun 9, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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