Kernel memory disclosure via vgem refcount race
Published May 31, 2022 · Updated Aug 3, 2024
Use-after-free in Linux kernel vgem before 5.6-rc2 allows local users with DRM access to disclose kernel memory via concurrent ioctls. DRM_IOCTL_MODE_DESTROY_DUMB can decrement the object's reference count while vgem_gem_dumb_create still accesses that object. Access to a vgem DRM device is required; the published PoC is unstable, and public evidence does not establish code execution or in-the-wild exploitation.
Summary
What happened
Use-after-free in Linux kernel vgem before 5.6-rc2 allows local users with DRM access to disclose kernel memory via concurrent ioctls. DRM_IOCTL_MODE_DESTROY_DUMB can decrement the object's reference count while vgem_gem_dumb_create still accesses that object. Access to a vgem DRM device is required; the published PoC is unstable, and public evidence does not establish code execution or in-the-wild exploitation.
The record
- CVE
- CVE-2022-1419
- Published
- May 31, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 31, 2022CVE 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=kernel 5.x
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.
Weakness, pattern, technique
Public exploit references
- Concurrent vgem ioctl proof of conceptproof 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