Kernel crash via premature device-running flag
Published Feb 29, 2024 · Updated May 11, 2026
Use of an uninitialized resource in the Linux QAT virtual-function driver allows local users to crash the kernel during device shutdown. The driver sets ADF_STATUS_PF_RUNNING before adf_dev_init succeeds, so shutdown can pass an uninitialized or destroyed vf2pf_lock to mutex_lock. Reachability requires Intel QAT virtual-function hardware, failed device initialization, and subsequent probe shutdown; the bounded consequence is a kernel crash.
Summary
What happened
Use of an uninitialized resource in the Linux QAT virtual-function driver allows local users to crash the kernel during device shutdown. The driver sets ADF_STATUS_PF_RUNNING before adf_dev_init succeeds, so shutdown can pass an uninitialized or destroyed vf2pf_lock to mutex_lock. Reachability requires Intel QAT virtual-function hardware, failed device initialization, and subsequent probe shutdown; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2021-47056
- Published
- Feb 29, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-908, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 29, 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=25c6ffb249f612c56a48ce48a3887adf57b8f4bd <05ec8192ee4bfdf2a8894a68350dac9f1a155fa6
- Affected versionversion=25c6ffb249f612c56a48ce48a3887adf57b8f4bd <09d16cee6285d37cc76311c29add6d97a7e4acda
- Affected versionversion=25c6ffb249f612c56a48ce48a3887adf57b8f4bd <1ea500ce6f7c9106e4a561d28e69215f3d451818
- Affected versionversion=25c6ffb249f612c56a48ce48a3887adf57b8f4bd <1f50392650ae794a1aea41c213c6a3e1c824413c
- Affected versionversion=25c6ffb249f612c56a48ce48a3887adf57b8f4bd <20fd40fc6f2c2b41dc6f637f88d494b14e9c21f1
- Affected versionversion=25c6ffb249f612c56a48ce48a3887adf57b8f4bd <446045cf682af12d9294765f6c46084b374b5654
- Affected versionversion=25c6ffb249f612c56a48ce48a3887adf57b8f4bd <8609f5cfdc872fc3a462efa6a3eca5cb1e2f6446
- Affected versionversion=25c6ffb249f612c56a48ce48a3887adf57b8f4bd <f4c4e07140687f42bfa40e091bb4a55d7960ce4d
- Affected versionversion=4.7
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