Vulnerability · Published Dec 24, 2025 · Assigned by Linux
CVE-2023-54097regulator: stm32-pwr: fix of_iomap leak
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 12% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: regulator: stm32-pwr: fix of_iomap leak Smatch reports: drivers/regulator/stm32-pwr.c:166 stm32_pwr_regulator_probe() warn: 'base' from of_iomap() not released on lines: 151,166. In stm32_pwr_regulator_probe(), base is not released when devm_kzalloc() fails to allocate memory or devm_regulator_register() fails to register a new regulator device, which may cause a leak. To fix this issue, replace of_iomap() with devm_platform_ioremap_resource(). devm_platform_ioremap_resource() is a specialized function for platform devices. It allows 'base' to be automatically released whether the probe function succeeds or fails. Besides, use IS_ERR(base) instead of !base as the return value of devm_platform_ioremap_resource() can either be a pointer to the remapped memory or an ERR_PTR() encoded error code if the operation fails.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.37-1 | DEBIAN-CVE-2023-54097 |
| Debian:13 | linux | 6.3.7-1 | DEBIAN-CVE-2023-54097 |
| Debian:14 | linux | 6.3.7-1 | DEBIAN-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux | 5.15.0-79.86 | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1042.47 | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1045.52 | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1045.52.1 | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1039.47 | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1039.44 | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1025.30 | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1035.38 | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1037.42 | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1039.44 | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-79.88 | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1030.30 | UBUNTU-CVE-2023-54097 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1016.16 | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1002.2 | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1040.46 | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1035.38 | UBUNTU-CVE-2023-54097 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-54097 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1025.29 | UBUNTU-CVE-2023-54097 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | dc62f951a6a8490bcccc7b6de36cd85bd57be740 – before 824683dbec234a01bd49a0589ee3323594a6f4cfdc62f951a6a8490bcccc7b6de36cd85bd57be740 – before dfce9bb3517a78507cf96f9b83948d0b81338afadc62f951a6a8490bcccc7b6de36cd85bd57be740 – before ad6481f49fb2c703efa3a929643934f24b666d6adc62f951a6a8490bcccc7b6de36cd85bd57be740 – before f25994f7a9ad53eb756bc4869497c3ebe281ad5edc62f951a6a8490bcccc7b6de36cd85bd57be740 – before c091bb49b3233307c7af73dae888f0799752af3ddc62f951a6a8490bcccc7b6de36cd85bd57be740 – before 0ad07e02be0d3f0d554653382ffe53ae4879378ddc62f951a6a8490bcccc7b6de36cd85bd57be740 – before c4a413e56d16a2ae84e6d8992f215c4dcc7fac20 |
| Linux | Linux | 5.2 |
References
- https://git.kernel.org/stable/c/824683dbec234a01bd49a0589ee3323594a6f4cf
- https://git.kernel.org/stable/c/dfce9bb3517a78507cf96f9b83948d0b81338afa
- https://git.kernel.org/stable/c/ad6481f49fb2c703efa3a929643934f24b666d6a
- https://git.kernel.org/stable/c/f25994f7a9ad53eb756bc4869497c3ebe281ad5e
- https://git.kernel.org/stable/c/c091bb49b3233307c7af73dae888f0799752af3d
- https://git.kernel.org/stable/c/0ad07e02be0d3f0d554653382ffe53ae4879378d
- https://git.kernel.org/stable/c/c4a413e56d16a2ae84e6d8992f215c4dcc7fac20