CVE-2023-53842: ASoC: codecs: wcd-mbhc-v2: fix resource leaks on component remove
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Fixed version: Linux Linux 17feff71d06c96dea1fa72451c20d411e9d5ac8f, 90ab6446eb522e31421b77bf8f45714f5668f9a3, a5475829adcc600bc69ee9ff7c9e3e43fb4f8d30.
Low priority for now. Upgrade to Linux Linux 17feff71d06c96dea1fa72451c20d411e9d5ac8f, 90ab6446eb522e31421b77bf8f45714f5668f9a3, a5475829adcc600bc69ee9ff7c9e3e43fb4f8d30 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Published
- Dec 9, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.14affected
- 0e5c9e7ff899808afa4e2b08c2e6ccc469bed681 and later · before 90ab6446eb522e31421b77bf8f45714f5668f9a3affected · git
- 0e5c9e7ff899808afa4e2b08c2e6ccc469bed681 and later · before 17feff71d06c96dea1fa72451c20d411e9d5ac8faffected · git
- 0e5c9e7ff899808afa4e2b08c2e6ccc469bed681 and later · before ce4059e1c0aca972446e06c09ee09a0d2ba5df54affected · git
- 0e5c9e7ff899808afa4e2b08c2e6ccc469bed681 and later · before a5475829adcc600bc69ee9ff7c9e3e43fb4f8d30affected · git
- before 5.14not affected · semver
- 5.15.123 and later · up to and including 5.15.*not affected · semver
- 6.1.42 and later · up to and including 6.1.*not affected · semver
- 6.4.7 and later · up to and including 6.4.*not affected · semver
- 6.5 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.52-1 | 6.1.52-1 |
| Debian:13 | linux | before 6.4.11-1 | 6.4.11-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-53840Dec 9, 2025 · usb: early: xhci-dbc: Fix a potential out-of-bound memory access0Monitor
- ← EarlierCVE-2023-53841Dec 9, 2025 · devlink: report devlink_port_type_warn source device0Monitor
- Later →CVE-2023-53843Dec 9, 2025 · net: openvswitch: reject negative ifindex0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 17feff71d06c96dea1fa72451c20d411e9d5ac8f | Vendor (CNA) |
| Linux Linux | 90ab6446eb522e31421b77bf8f45714f5668f9a3 | Vendor (CNA) |
| Linux Linux | a5475829adcc600bc69ee9ff7c9e3e43fb4f8d30 | Vendor (CNA) |
| Linux Linux | ce4059e1c0aca972446e06c09ee09a0d2ba5df54 | Vendor (CNA) |
| debian:linux | 6.1.52-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.