CVE-2023-54072

ALSA: pcm: Fix potential data race at PCM memory allocation helpers

N/A
Published: December 24, 2025 at 12:23 PM UTC
Updated: June 17, 2026 at 06:46 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Fix potential data race at PCM memory allocation helpers The PCM memory allocation helpers have a sanity check against too many buffer allocations. However, the check is performed without a proper lock and the allocation isn't serialized; this allows user to allocate more memories than predefined max size. Practically seen, this isn't really a big problem, as it's more or less some "soft limit" as a sanity check, and it's not possible to allocate unlimitedly. But it's still better to address this for more consistent behavior. The patch covers the size check in do_alloc_pages() with the card->memory_mutex, and increases the allocated size there for preventing the further overflow. When the actual allocation fails, the size is decreased accordingly.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.6 ≤ v < 5.10.1935.6 ≤ v < 5.15.1295.6 ≤ v < 6.1.395.6 ≤ v < 6.4.45.6 ≤ v < 6.55.695b30a4312545f2dde9db12bf6a425f35d5a0d77d4cfb30fce03093ad944e0b44bd8f40bdad5330e
Vendor states this is fixed in 3eb4e47a94e3f76521d7d344696db61e6a9619c7 (fixed)
Vendor states this is fixed in 773ccad902f67583a58b5650a2f8d8daf2e76fac (fixed)
Vendor states this is fixed in 7e11c58b2620a22c67a5ae28d64ce383890ee9f4 (fixed)
Vendor states this is fixed in 7e1d1456c8db9949459c5a24e8845cfe92430b0f (fixed)
Vendor states this is fixed in a0ab49e7a758b488b2090171a75d50735c0876f6 (fixed)
Vendor states this is fixed in bd55842ed998a622ba6611fe59b3358c9f76773d (fixed)
Vendor states this is fixed in 5.10.193 (unaffected)
Vendor states this is fixed in 5.15.129 (unaffected)
Vendor states this is fixed in 5.6 (unaffected)
Vendor states this is fixed in 6.1.39 (unaffected)
Vendor states this is fixed in 6.4.4 (unaffected)
Vendor states this is fixed in 6.5 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card