LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52697: ASoC: Intel: sof_sdw_rt_sdca_jack_common: ctx->headset_codec_dev = NULL

In the Linux kernel, the following vulnerability has been resolved: ASoC: Intel: sof_sdw_rt_sdca_jack_common: ctx->headset_codec_dev = NULL sof_sdw_rt_sdca_jack_exit() are used by different codecs, and some of them use the same dai name. For example, rt712 and rt713 both use "rt712-sdca-aif1" and sof_sdw_rt_sdca_jack_exit(). As a result, sof_sdw_rt_sdca_jack_exit() will be called twice by mc_dailink_exit_loop(). Set ctx->headset_codec_dev = NULL; after put_device(ctx->headset_codec_dev); to avoid ctx->headset_codec_dev being put twice.

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-52697 is a Linux kernel audio-driver flaw in Intel SoundWire/ASoC handling. Certain Realtek SDCA codec combinations can trigger cleanup that releases the same headset codec device twice. Sources describe a kernel safety/reliability bug fixed in stable commits, but not real-world impact or exploitation. Prioritize affected kernel inventory over emergency response.

Executive priority

Treat as a routine kernel maintenance item unless your fleet includes many affected audio-enabled Linux endpoints. There is no cited active exploitation, CVSS, or business-impact detail, so urgency should be driven by exposure inventory and vendor patch availability.

Technical view

In sof_sdw_rt_sdca_jack_exit(), used by multiple codecs including rt712 and rt713 sharing the same DAI name, mc_dailink_exit_loop() can call cleanup twice. The fix sets ctx->headset_codec_dev to NULL after put_device(), preventing a second put. The bundle lists Linux kernel versions including 6.5, 6.6.14, 6.7.2, and 6.8 as affected.

Likely exposure

Most relevant to systems running Linux kernels with Intel ASoC SoundWire audio paths and the involved Realtek SDCA codecs. Server exposure may be lower if that hardware and driver path are absent. The bundle does not indicate network exposure.

Exploitation context

No active exploitation is indicated: KEV is false, and the source bundle provides no exploit reports or proof-of-concept status. The described condition is local kernel driver cleanup behavior, not a remote service flaw, but consequences are not fully described.

Researcher notes

Evidence is narrow: three kernel stable commits and the CVE record describe a double put in an Intel ASoC SoundWire jack cleanup path. No CWE, CVSS, exploitability analysis, crash proof, or privilege-impact statement is supplied. Avoid assuming remote exploitability or broader Linux impact without vendor confirmation.

Mitigation direction

  • Check distribution advisories for CVE-2023-52697 and apply the relevant kernel update.
  • Confirm whether kernel packages include one of the referenced stable commits.
  • Prioritize laptops and workstations using Intel SoundWire audio with Realtek SDCA codec paths.
  • If no vendor package is available, follow kernel vendor guidance for supported backports.

Validation and detection

  • Inventory running kernel versions across endpoints and servers.
  • Identify systems with Intel ASoC SoundWire audio drivers enabled or loaded.
  • Compare installed kernel changelogs against the referenced stable commit IDs.
  • Review vulnerability scanner results for distribution-specific CVE mapping.
  • Document systems where the hardware path is absent as lower exposure.
Prepared
Confidence
medium
Sources
5

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-2023-52697 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
4Source 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
LinuxLinux5360c67046385f90406ec17e367ba9aeb42d5459, 5360c67046385f90406ec17e367ba9aeb42d5459, 5360c67046385f90406ec17e367ba9aeb42d5459unaffected
LinuxLinux6.5, 0, 6.6.14, 6.7.2, 6.8affected
Weakness

CWE details

No CWE listed

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