Vulnerability · Published Dec 24, 2025 · Assigned by Linux
CVE-2023-54072ALSA: pcm: Fix potential data race at PCM memory allocation helpers
Unrated
In plain English
A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 11% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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 packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.52-1 | DEBIAN-CVE-2023-54072 |
| Debian:13 | linux | 6.4.4-1 | DEBIAN-CVE-2023-54072 |
| Debian:14 | linux | 6.4.4-1 | DEBIAN-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux | 5.15.0-91.101 | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1051.56 | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1053.61 | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1053.61.1 | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1048.56 | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1048.53 | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1034.40 | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1044.47 | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1046.52 | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1048.53 | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-91.101 | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1042.42 | UBUNTU-CVE-2023-54072 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1020.20 | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1007.7 | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1049.55 | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1044.47 | UBUNTU-CVE-2023-54072 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-54072 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1027.31 | UBUNTU-CVE-2023-54072 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 95b30a4312545f2dde9db12bf6a425f35d5a0d77 – before 7e1d1456c8db9949459c5a24e8845cfe92430b0fd4cfb30fce03093ad944e0b44bd8f40bdad5330e – before 7e11c58b2620a22c67a5ae28d64ce383890ee9f4d4cfb30fce03093ad944e0b44bd8f40bdad5330e – before a0ab49e7a758b488b2090171a75d50735c0876f6d4cfb30fce03093ad944e0b44bd8f40bdad5330e – before 3eb4e47a94e3f76521d7d344696db61e6a9619c7d4cfb30fce03093ad944e0b44bd8f40bdad5330e – before 773ccad902f67583a58b5650a2f8d8daf2e76facd4cfb30fce03093ad944e0b44bd8f40bdad5330e – before bd55842ed998a622ba6611fe59b3358c9f76773d |
| Linux | Linux | 5.6 |
References
- https://git.kernel.org/stable/c/7e1d1456c8db9949459c5a24e8845cfe92430b0f
- https://git.kernel.org/stable/c/7e11c58b2620a22c67a5ae28d64ce383890ee9f4
- https://git.kernel.org/stable/c/a0ab49e7a758b488b2090171a75d50735c0876f6
- https://git.kernel.org/stable/c/3eb4e47a94e3f76521d7d344696db61e6a9619c7
- https://git.kernel.org/stable/c/773ccad902f67583a58b5650a2f8d8daf2e76fac
- https://git.kernel.org/stable/c/bd55842ed998a622ba6611fe59b3358c9f76773d