System crash or one-bit disclosure via stale dentry
Published Jan 28, 2020 · Updated Aug 4, 2024
Use-after-free in Linux kernel 4.19 through 5.4 allows local users to crash the system or expose one bit of kernel-memory state. During concurrent open, rename, and parent-directory removal operations, do_last drops the directory reference before may_create_in_sticky reads its dentry and inode. The race requires local syscall access; the stale reads produce a kernel Oops or a one-bit access-decision oracle rather than arbitrary kernel-memory disclosure.
Summary
What happened
Use-after-free in Linux kernel 4.19 through 5.4 allows local users to crash the system or expose one bit of kernel-memory state. During concurrent open, rename, and parent-directory removal operations, do_last drops the directory reference before may_create_in_sticky reads its dentry and inode. The race requires local syscall access; the stale reads produce a kernel Oops or a one-bit access-decision oracle rather than arbitrary kernel-memory disclosure.
The record
- CVE
- CVE-2020-8428
- Published
- Jan 28, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 28, 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
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