LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53842: ASoC: codecs: wcd-mbhc-v2: fix resource leaks on component remove

In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: wcd-mbhc-v2: fix resource leaks on component remove The MBHC resources must be released on component probe failure and removal so can not be tied to the lifetime of the component device. This is specifically needed to allow probe deferrals of the sound card which otherwise fails when reprobing the codec component: snd-sc8280xp sound: ASoC: failed to instantiate card -517 genirq: Flags mismatch irq 299. 00002001 (mbhc sw intr) vs. 00002001 (mbhc sw intr) wcd938x_codec audio-codec: Failed to request mbhc interrupts -16 wcd938x_codec audio-codec: mbhc initialization failed wcd938x_codec audio-codec: ASoC: error at snd_soc_component_probe on audio-codec: -16 snd-sc8280xp sound: ASoC: failed to instantiate card -16

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a resource cleanup bug in an audio codec path. On affected systems, sound card probing can fail after deferral or removal because MBHC interrupt resources were not released correctly. The likely business impact is device audio availability, not broad remote compromise.

Executive priority

Treat as a low-priority maintenance fix unless affected systems depend on reliable audio initialization. Include it in normal kernel update cycles, with higher priority for embedded or endpoint fleets using the impacted audio codec path.

Technical view

The flaw is in ASoC codecs wcd-mbhc-v2. MBHC resources were tied to the component device lifetime, leaving resources behind on probe failure or component removal. Reprobe can then hit IRQ conflicts and fail codec initialization, as shown by the kernel log examples in the CVE description.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the relevant ASoC wcd-mbhc-v2 codec path, including wcd938x-style audio codec use. The bundle does not identify a remote attack surface or affected distributions.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. The described failure mode is operational: leaked resources prevent successful audio codec reprobe and sound card instantiation.

Researcher notes

The fix releases MBHC resources during component probe failure and removal instead of tying them to component device lifetime. Evidence is limited to the CVE description and stable kernel references; no CVSS, CWE, exploitability, or distro-specific fix details are supplied.

Mitigation direction

  • Update to a kernel release containing the referenced stable fixes.
  • Check Linux vendor guidance for distribution-specific fixed packages.
  • Prioritize devices using the affected ASoC wcd-mbhc-v2 codec path.
  • Monitor vendor advisories if running kernels listed as affected.

Validation and detection

  • Inventory kernel versions against the affected version data in the CVE bundle.
  • Confirm whether systems use the wcd-mbhc-v2 or related wcd938x audio codec path.
  • Review kernel package changelogs for the referenced stable commit IDs.
  • Check system logs for MBHC interrupt conflicts or codec initialization failures.
Prepared
Confidence
medium
Sources
6

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-53842 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
0ADP providers
5Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0e5c9e7ff899808afa4e2b08c2e6ccc469bed681, 0e5c9e7ff899808afa4e2b08c2e6ccc469bed681, 0e5c9e7ff899808afa4e2b08c2e6ccc469bed681, 0e5c9e7ff899808afa4e2b08c2e6ccc469bed681unaffected
LinuxLinux5.14, 0, 5.15.123, 6.1.42, 6.4.7, 6.5affected
Weakness

CWE details

No CWE listed

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