System crash via nouveau postclose use-after-free
Published Nov 2, 2021 · Updated Aug 4, 2024
Use-after-free in the Linux kernel nouveau driver allows attackers to crash the system by unbinding or removing a graphics device. Device removal frees the entire nouveau_drm structure while userspace can retain an open device file, so postclose() later dereferences freed memory. Exploitation requires privileged local access to unbind the driver or physical proximity to remove a bound graphics device.
Summary
What happened
Use-after-free in the Linux kernel nouveau driver allows attackers to crash the system by unbinding or removing a graphics device. Device removal frees the entire nouveau_drm structure while userspace can retain an open device file, so postclose() later dereferences freed memory. Exploitation requires privileged local access to unbind the driver or physical proximity to remove a bound graphics device.
The record
- CVE
- CVE-2020-27820
- Published
- Nov 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 2, 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=to be fixed in RHEL-9 release
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
- IGT core_hotunplug reproduction procedureproof 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