Vulnerability · Published Sep 16, 2025 · Assigned by Linux
CVE-2023-53275ALSA: hda: fix a possible null-pointer dereference due to data race in snd_hdac_regmap_sync()
Medium 5.5
In plain English
A medium-severity null pointer dereference 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 5% 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: hda: fix a possible null-pointer dereference due to data race in snd_hdac_regmap_sync() The variable codec->regmap is often protected by the lock codec->regmap_lock when is accessed. However, it is accessed without holding the lock when is accessed in snd_hdac_regmap_sync(): if (codec->regmap) In my opinion, this may be a harmful race, because if codec->regmap is set to NULL right after the condition is checked, a null-pointer dereference can occur in the called function regcache_sync(): map->lock(map->lock_arg); --> Line 360 in drivers/base/regmap/regcache.c To fix this possible null-pointer dereference caused by data race, the mutex_lock coverage is extended to protect the if statement as well as the function call to regcache_sync(). [ Note: the lack of the regmap_lock itself is harmless for the current codec driver implementations, as snd_hdac_regmap_sync() is only for PM runtime resume that is prohibited during the codec probe. But the change makes the whole code more consistent, so it's merged as is -- tiwai ]
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.52-1 | DEBIAN-CVE-2023-53275 |
| Debian:13 | linux | 6.4.13-1 | DEBIAN-CVE-2023-53275 |
| Debian:14 | linux | 6.4.13-1 | DEBIAN-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux | 5.15.0-91.101 | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1051.56 | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1053.61 | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1053.61.1 | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1048.56 | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1048.53 | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1034.40 | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1044.47 | UBUNTU-CVE-2023-53275 |
| Ubuntu:24.04:LTS | linux-intel | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1046.52 | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1048.53 | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-91.101 | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1042.42 | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1020.20 | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1007.7 | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1049.55 | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1044.47 | UBUNTU-CVE-2023-53275 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-53275 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1027.31 | UBUNTU-CVE-2023-53275 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 69d5dc286d05441ca2f854ae8df11201f6f9b706 – before 109f0aaa0b8838a88af9125b79579023539300a71a462be52f4505a2719631fb5aa7bfdbd37bfd8d – before 9f9eed451176ffcac6b5ba0f6dae1a6b4a1cb0eb1a462be52f4505a2719631fb5aa7bfdbd37bfd8d – before 8703b26387e1fa4f8749db98d24c67617b873acb1a462be52f4505a2719631fb5aa7bfdbd37bfd8d – before cdd412b528dee6e0851c4735d6676ec138da13a41a462be52f4505a2719631fb5aa7bfdbd37bfd8d – before b32e40379e5b2814de0c4bc199edc2d82317dc071a462be52f4505a2719631fb5aa7bfdbd37bfd8d – before 1f4a08fed450db87fbb5ff5105354158bdbe1a225.4.43 – before 5.4.255 |
| Linux | Linux | 5.6 |
Weakness: CWE-476 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
References
- https://git.kernel.org/stable/c/109f0aaa0b8838a88af9125b79579023539300a7
- https://git.kernel.org/stable/c/9f9eed451176ffcac6b5ba0f6dae1a6b4a1cb0eb
- https://git.kernel.org/stable/c/8703b26387e1fa4f8749db98d24c67617b873acb
- https://git.kernel.org/stable/c/cdd412b528dee6e0851c4735d6676ec138da13a4
- https://git.kernel.org/stable/c/b32e40379e5b2814de0c4bc199edc2d82317dc07
- https://git.kernel.org/stable/c/1f4a08fed450db87fbb5ff5105354158bdbe1a22