Private-memory disclosure via stale page mappings
Published Apr 7, 2021 · Updated Aug 3, 2024
Use-after-free in FreeBSD before 13.0-RC5-p1, 12.2-RELEASE-p6, or 11.4-RELEASE-p9 allows local users to read private memory. The VM copy-on-write path fails to invalidate sibling mappings of a source page after a descendant process writes, leaving mappings valid after page reuse. An unprivileged local user can construct the ancestor-descendant sharing relationship and read data later assigned to another process or the kernel.
Summary
What happened
Use-after-free in FreeBSD before 13.0-RC5-p1, 12.2-RELEASE-p6, or 11.4-RELEASE-p9 allows local users to read private memory. The VM copy-on-write path fails to invalidate sibling mappings of a source page after a descendant process writes, leaving mappings valid after page reuse. An unprivileged local user can construct the ancestor-descendant sharing relationship and read data later assigned to another process or the kernel.
The record
- CVE
- CVE-2021-29626
- Published
- Apr 7, 2021
- Updated
- Aug 3, 2024
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-416, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 7, 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=FreeBSD 12.2-RELEASE before p6, 11.4-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.
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