Memory leak via unreleased event sources
Published Jan 21, 2020 · Updated Jun 9, 2025
Memory leak in systemd before 243 allows physically proximate attackers to consume systemd-logind memory through power-switch udev events. button_open replaces b->io_event_source with a new event source without first releasing the existing reference, so repeated change events leak memory. Reachability requires physical hardware events or root execution of udevadm trigger, and Red Hat reports that crashing logind is difficult.
Summary
What happened
Memory leak in systemd before 243 allows physically proximate attackers to consume systemd-logind memory through power-switch udev events. button_open replaces b->io_event_source with a new event source without first releasing the existing reference, so repeated change events leak memory. Reachability requires physical hardware events or root execution of udevadm trigger, and Red Hat reports that crashing logind is difficult.
The record
- CVE
- CVE-2019-20386
- Published
- Jan 21, 2020
- Updated
- Jun 9, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2020CVE 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