Kernel memory overwrite via cryptodev use-after-free
Published May 13, 2020 · Updated Aug 5, 2024
Use-after-free in the FreeBSD cryptodev module allows local users to overwrite arbitrary kernel memory through a race condition. The race leaves a kernel data structure reachable after cryptodev frees it, so an unprivileged process can continue using stale storage for kernel-memory writes. Exploitation requires an unprivileged local process and 12.1-STABLE before r356908, 12.1-RELEASE before p5, 11.3-STABLE before r356908, or 11.3-RELEASE before p9.
Summary
What happened
Use-after-free in the FreeBSD cryptodev module allows local users to overwrite arbitrary kernel memory through a race condition. The race leaves a kernel data structure reachable after cryptodev frees it, so an unprivileged process can continue using stale storage for kernel-memory writes. Exploitation requires an unprivileged local process and 12.1-STABLE before r356908, 12.1-RELEASE before p5, 11.3-STABLE before r356908, or 11.3-RELEASE before p9.
The record
- CVE
- CVE-2019-15879
- Published
- May 13, 2020
- Updated
- Aug 5, 2024
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-362, CWE-772, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 13, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=FreeBSD 12.1-RELEASE before p5, and 11.3-RELEASE before p9
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