Local system crash via stale mm pointer
Published Jan 7, 2021 · Updated Aug 4, 2024
Use-after-free in the Linux Kernel hfi1 driver before 5.10-rc6 allows local users to crash the system through ioctl calls after fork. The driver caches current->mm when an hfi1 device file is opened, but a forked child can inherit the descriptor and use the parent's memory context after its reference is released. Access to an hfi1 device file and high local privileges are required, and the bounded reported consequence is a kernel crash.
Summary
What happened
Use-after-free in the Linux Kernel hfi1 driver before 5.10-rc6 allows local users to crash the system through ioctl calls after fork. The driver caches current->mm when an hfi1 device file is opened, but a forked child can inherit the descriptor and use the parent's memory context after its reference is released. Access to an hfi1 device file and high local privileges are required, and the bounded reported consequence is a kernel crash.
The record
- CVE
- CVE-2020-27835
- Published
- Jan 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 7, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=kernel versions prior to 5.10-rc6
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