Kernel crash via unflushed lockup workqueue
Published May 3, 2024 · Updated May 11, 2026
Race condition in the Linux kernel Radeon driver allows local users to crash the kernel during Radeon device suspension. The radeon_suspend_kms function can place the PCI device in D3hot before delayed lockup work is fully flushed, causing the worker to access the powered-down GPU. A local low-privileged user must reach the suspend race on a system using the Radeon driver; successful exploitation causes a kernel Oops and service interruption.
Summary
What happened
Race condition in the Linux kernel Radeon driver allows local users to crash the kernel during Radeon device suspension. The radeon_suspend_kms function can place the PCI device in D3hot before delayed lockup work is fully flushed, causing the worker to access the powered-down GPU. A local low-privileged user must reach the suspend race on a system using the Radeon driver; successful exploitation causes a kernel Oops and service interruption.
The record
- CVE
- CVE-2022-48704
- Published
- May 3, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 3, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=0bfa4b41268ad5fd741f16f484e4fee190822ec6 <16cb367daa446923d82e332537f446a4cc784b40
- Affected versionversion=0bfa4b41268ad5fd741f16f484e4fee190822ec6 <4e25e8f27fdbdc6fd55cc572a9939bf24500b9e8
- Affected versionversion=0bfa4b41268ad5fd741f16f484e4fee190822ec6 <5a7a5b2edac4b05abd744eeaebda46d9dacd952d
- Affected versionversion=0bfa4b41268ad5fd741f16f484e4fee190822ec6 <826b46fd5974113515abe9e4fc8178009a8ce18c
- Affected versionversion=0bfa4b41268ad5fd741f16f484e4fee190822ec6 <b878da58df2c40b08914d3960e2224040fd1fbfe
- Affected versionversion=0bfa4b41268ad5fd741f16f484e4fee190822ec6 <c0a45f41fde4a0f2c900f719817493ee5c4a5aa3
- Affected versionversion=0bfa4b41268ad5fd741f16f484e4fee190822ec6 <c72d97146fc5a4dff381b1737f6167e89860430d
- Affected versionversion=0bfa4b41268ad5fd741f16f484e4fee190822ec6 <f461950fdc374a3ada5a63c669d997de4600dffe
- Affected versionversion=3.18
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
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