Local heap corruption via tagged brk address
Published Feb 25, 2020 · Updated Aug 4, 2024
Memory corruption in the AArch64 Linux kernel 5.4 and 5.5 through 5.5.6 allows local users to corrupt a glibc heap via brk. The arm64 brk path strips the top address byte instead of rejecting an address beyond the 56-bit limit, allowing the program break to move downward when malloc expects an upward move. Reachability requires an AArch64 system and a local process using glibc malloc; the demonstrated consequence is process heap corruption and a crash.
Summary
What happened
Memory corruption in the AArch64 Linux kernel 5.4 and 5.5 through 5.5.6 allows local users to corrupt a glibc heap via brk. The arm64 brk path strips the top address byte instead of rejecting an address beyond the 56-bit limit, allowing the program break to move downward when malloc expects an upward move. Reachability requires an AArch64 system and a local process using glibc malloc; the demonstrated consequence is process heap corruption and a crash.
The record
- CVE
- CVE-2020-9391
- Published
- Feb 25, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 25, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- AArch64 glibc malloc crash reproducerproof of concept · demonstrated
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