CVE-2023-54072
ALSA: pcm: Fix potential data race at PCM memory allocation helpers
- Published
- Updated
- Reserved
- Assigned by
- Linux
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.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (7 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 95b30a4312545f2dde9db12bf6a425f35d5a0d77 – < 7e1d1456c8db9949459c5a24e8845cfe92430b0f
- affected d4cfb30fce03093ad944e0b44bd8f40bdad5330e – < 7e11c58b2620a22c67a5ae28d64ce383890ee9f4
- affected d4cfb30fce03093ad944e0b44bd8f40bdad5330e – < a0ab49e7a758b488b2090171a75d50735c0876f6
- affected d4cfb30fce03093ad944e0b44bd8f40bdad5330e – < 3eb4e47a94e3f76521d7d344696db61e6a9619c7
- affected d4cfb30fce03093ad944e0b44bd8f40bdad5330e – < 773ccad902f67583a58b5650a2f8d8daf2e76fac
- affected d4cfb30fce03093ad944e0b44bd8f40bdad5330e – < bd55842ed998a622ba6611fe59b3358c9f76773d
- affected 5.6
- unaffected < 5.6
- unaffected 5.10.193 – ≤ 5.10.*
- unaffected 5.15.129 – ≤ 5.15.*
- unaffected 6.1.39 – ≤ 6.1.*
- unaffected 6.4.4 – ≤ 6.4.*
- unaffected 6.5 – ≤ *
References (6)
- https://git.kernel.org/stable/c/7e1d1456c8db9949459c5a24e8845cfe92430b0f (opens in a new tab)
- https://git.kernel.org/stable/c/7e11c58b2620a22c67a5ae28d64ce383890ee9f4 (opens in a new tab)
- https://git.kernel.org/stable/c/a0ab49e7a758b488b2090171a75d50735c0876f6 (opens in a new tab)
- https://git.kernel.org/stable/c/3eb4e47a94e3f76521d7d344696db61e6a9619c7 (opens in a new tab)
- https://git.kernel.org/stable/c/773ccad902f67583a58b5650a2f8d8daf2e76fac (opens in a new tab)
- https://git.kernel.org/stable/c/bd55842ed998a622ba6611fe59b3358c9f76773d (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2023-54072)Record last updated .