LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47037: ASoC: q6afe-clocks: fix reprobing of the driver

In the Linux kernel, the following vulnerability has been resolved: ASoC: q6afe-clocks: fix reprobing of the driver Q6afe-clocks driver can get reprobed. For example if the APR services are restarted after the firmware crash. However currently Q6afe-clocks driver will oops because hw.init will get cleared during first _probe call. Rewrite the driver to fill the clock data at runtime rather than using big static array of clocks.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash affected systems when the q6afe-clocks driver is probed again after APR services restart, such as after a firmware crash. The provided sources do not give a CVSS score or exploitation evidence, so urgency depends on whether your kernels include and use this driver path.

Executive priority

Treat this as a targeted kernel reliability risk, not a confirmed exploited emergency. Patch through normal security maintenance, escalating for fleets that use affected Qualcomm audio-related kernel paths or have observed firmware crash and APR restart instability.

Technical view

The q6afe-clocks driver could oops on reprobe because hw.init is cleared during the first probe. The fix changes clock data setup to occur at runtime instead of relying on a large static clock array. Affected ranges include Linux 5.10 through before fixed stable releases listed in the CVE bundle.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions that include and exercise the q6afe-clocks driver, particularly when APR services restart after firmware failure. The bundle does not identify specific distributions, devices, or cloud images beyond Linux kernel references and a Debian LTS advisory link.

Exploitation context

The CVE is not listed as KEV in the bundle, and no cited source states active exploitation. The described failure is a kernel oops during driver reprobing after firmware-related service restart. The provided evidence does not establish remote reachability or public exploit availability.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or detailed affected product matrix is provided. Analysis should stay anchored to the kernel fix rationale: reprobe after APR restart can oops because probe-time clock initialization state is invalidated.

Mitigation direction

  • Update affected Linux kernels using vendor or distribution security guidance.
  • Confirm the installed kernel contains one of the referenced stable fixes.
  • Review Debian LTS guidance if operating Debian-based affected systems.
  • Prioritize systems where q6afe-clocks is present and APR restart events occur.
  • Use normal kernel rollback testing before broad production deployment.

Validation and detection

  • Inventory Linux kernel versions against affected and fixed ranges in the CVE bundle.
  • Check whether the q6afe-clocks driver is built or loaded on target systems.
  • Review kernel logs for q6afe, APR restart, firmware crash, or oops events.
  • Verify vendor kernel packages reference CVE-2021-47037 or the stable commits.
  • Retest firmware-restart scenarios in a controlled environment after updating.
Prepared
Confidence
medium
Sources
7

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-47037 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
6Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux520a1c396d1966b64884d8e0176a580150d5a09e, 520a1c396d1966b64884d8e0176a580150d5a09e, 520a1c396d1966b64884d8e0176a580150d5a09e, 520a1c396d1966b64884d8e0176a580150d5a09eunaffected
LinuxLinux5.10, 0, 5.10.238, 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.