LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47056: crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init

In the Linux kernel, the following vulnerability has been resolved: crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init ADF_STATUS_PF_RUNNING is (only) used and checked by adf_vf2pf_shutdown() before calling adf_iov_putmsg()->mutex_lock(vf2pf_lock), however the vf2pf_lock is initialized in adf_dev_init(), which can fail and when it fail, the vf2pf_lock is either not initialized or destroyed, a subsequent use of vf2pf_lock will cause issue. To fix this issue, only set this flag if adf_dev_init() returns 0. [ 7.178404] BUG: KASAN: user-memory-access in __mutex_lock.isra.0+0x1ac/0x7c0 [ 7.180345] Call Trace: [ 7.182576] mutex_lock+0xc9/0xd0 [ 7.183257] adf_iov_putmsg+0x118/0x1a0 [intel_qat] [ 7.183541] adf_vf2pf_shutdown+0x4d/0x7b [intel_qat] [ 7.183834] adf_dev_shutdown+0x172/0x2b0 [intel_qat] [ 7.184127] adf_probe+0x5e9/0x600 [qat_dh895xccvf]

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2021-47056 is a Linux kernel bug in the Intel QAT driver. During a failed device initialization path, shutdown code can try to lock a mutex that was not successfully initialized or was already destroyed, causing a kernel fault. The source does not provide CVSS, confirmed exploitation, or attacker prerequisites.

Executive priority

Handle as a targeted kernel maintenance issue, not an emergency based on current evidence. Prioritize systems that depend on Intel QAT acceleration or QAT virtualization because failures occur in kernel driver initialization and shutdown paths.

Technical view

The QAT driver set ADF_STATUS_PF_RUNNING before adf_dev_init() completed. If adf_dev_init() failed, adf_vf2pf_shutdown() could call adf_iov_putmsg() and mutex_lock(vf2pf_lock) on invalid lock state. The upstream fix sets the PF_RUNNING flag only after adf_dev_init() returns 0.

Likely exposure

Exposure is most likely on Linux systems using Intel QAT drivers, especially affected kernel branches listed by the CVE record. Systems without QAT hardware, drivers, or virtualization paths using qat_dh895xccvf appear less likely to be exposed, but the provided sources do not define exact deployment prerequisites.

Exploitation context

The source bundle shows a KASAN kernel fault during probe/shutdown error handling. It does not cite public exploitation, weaponized proof of concept, or inclusion in CISA KEV. Treat active exploitation as unconfirmed.

Researcher notes

Evidence is narrow: the public record describes a flag-ordering bug and a KASAN trace, but not reachability from unprivileged users or remote actors. Analysis should focus on QAT driver load paths, VF/PF shutdown behavior, and whether vendor kernels carry the stable fix.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable QAT fixes.
  • Prioritize hosts using Intel QAT hardware or QAT virtual functions.
  • Check your distribution vendor advisories for backported kernel packages.
  • Disable unused QAT driver exposure where operationally acceptable.
  • Track this through normal kernel vulnerability management until patched.

Validation and detection

  • Inventory Linux hosts for Intel QAT hardware and loaded QAT modules.
  • Map running kernel versions against the CVE record and vendor advisories.
  • Confirm patched kernels include the referenced stable commits or distro backports.
  • Review boot and kernel logs for QAT probe or shutdown faults.
  • Validate updates in staging before production rollout.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-47056 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux25c6ffb249f612c56a48ce48a3887adf57b8f4bd, 25c6ffb249f612c56a48ce48a3887adf57b8f4bd, 25c6ffb249f612c56a48ce48a3887adf57b8f4bd, 25c6ffb249f612c56a48ce48a3887adf57b8f4bd, 25c6ffb249f612c56a48ce48a3887adf57b8f4bd, 25c6ffb249f612c56a48ce48a3887adf57b8f4bd, 25c6ffb249f612c56a48ce48a3887adf57b8f4bd, 25c6ffb249f612c56a48ce48a3887adf57b8f4bdunaffected
LinuxLinux4.7, 0, 4.9.269, 4.14.233, 4.19.191, 5.4.119, 5.10.37, 5.11.21, 5.12.4, 5.13affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.