CVE-2023-54245: ASoC: codecs: tx-macro: Fix for KASAN: slab-out-of-bounds
In the Linux kernel, the following vulnerability has been resolved:
ASoC: codecs: tx-macro: Fix for KASAN: slab-out-of-bounds
When we run syzkaller we get below Out of Bound.
"KASAN: slab-out-of-bounds Read in regcache_flat_read"
Below is the backtrace of the issue:
dump_backtrace+0x0/0x4c8
show_stack+0x34/0x44
dump_stack_lvl+0xd8/0x118
print_address_description+0x30/0x2d8
kasan_report+0x158/0x198
__asan_report_load4_noabort+0x44/0x50
regcache_flat_read+0x10c/0x110
regcache_read+0xf4/0x180
_regmap_read+0xc4/0x278
_regmap_update_bits+0x130/0x290
regmap_update_bits_base+0xc0/0x15c
snd_soc_component_update_bits+0xa8/0x22c
snd_soc_component_write_field+0x68/0xd4
tx_macro_digital_mute+0xec/0x140
Actually There is no need to have decimator with 32 bits.
By limiting the variable with short type u8 issue is resolved.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel audio driver memory-safety issue found by automated testing. The documented symptom is a kernel out-of-bounds read, not a publicly described attack path. Business urgency depends on whether your fleet runs affected Linux kernel versions with this driver path present.
Executive priority
Treat this as a kernel maintenance item requiring exposure confirmation, not an emergency based on current evidence. Escalate if affected kernels are broadly deployed on business-critical systems or vendor advisories add exploitability details.
Technical view
CVE-2023-54245 concerns the Linux ASoC tx-macro codec code. Syzkaller triggered a KASAN slab-out-of-bounds read in regcache_flat_read through tx_macro_digital_mute. The fix limits a decimator-related variable to u8 because 32 bits were unnecessary. CVSS, CWE, and exploitability details are not provided in the source bundle.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel versions where the ASoC tx-macro codec code is built or loadable. The bundle lists Linux kernel 5.12 through later affected release points, with stable kernel commit references for fixes.
Exploitation context
The source bundle marks KEV as false and provides no evidence of active exploitation or a public exploit. The issue was discovered through syzkaller and KASAN testing, so exploitation risk cannot be reliably rated from these sources alone.
Researcher notes
The evidence describes an out-of-bounds read in regcache_flat_read reached via tx_macro_digital_mute. The fix rationale is type narrowing to u8. Missing CVSS, CWE, and attack prerequisites prevent strong conclusions about impact or exploitability.
Mitigation direction
Apply vendor or Linux stable kernel updates containing the referenced tx-macro fix.
Prioritize affected systems where the ASoC tx-macro codec driver is present.
If patching is delayed, check vendor guidance for supported mitigations.
Avoid inventing local workarounds without vendor or kernel maintainer validation.
Validation and detection
Inventory Linux kernel versions against the CVE affected-version data.
Check whether ASoC tx-macro codec code is built, loaded, or packaged.
Confirm deployed kernels include one of the referenced stable fixes.
Review kernel crash logs for related KASAN or slab-out-of-bounds reports.
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-54245 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 30, 2025, 12:15 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.