Linux Kernel up to 6.3.1 regulator stm32-pwr.c stm32_pwr_regulator_probe return value

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 6.3.1. It has been classified as critical. Affected by this vulnerability is the function stm32_pwr_regulator_probe of the file drivers/regulator/stm32-pwr.c of the component regulator. The manipulation leads to return value.
This vulnerability is listed as CVE-2023-54097. There is no available exploit.
Upgrading the affected component is recommended.
Details
A vulnerability was found in Linux Kernel up to 6.3.1 and classified as critical. This issue affects the function stm32_pwr_regulator_probe of the file drivers/regulator/stm32-pwr.c of the component regulator. The manipulation with an unknown input leads to a return value vulnerability. Using CWE to declare the problem leads to CWE-252. The product does not check the return value from a method or function, which can prevent it from detecting unexpected states and conditions. Impacted is availability. The summary by CVE is:
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.
It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2023-54097 since 12/24/2025. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/03/2026).
The vulnerability scanner Nessus provides a plugin with the ID 279759 (Linux Distros Unpatched Vulnerability : CVE-2023-54097), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.4.243, 5.10.180, 5.15.111, 6.1.28, 6.2.15 or 6.3.2 eliminates this vulnerability. Applying the patch 824683dbec234a01bd49a0589ee3323594a6f4cf/dfce9bb3517a78507cf96f9b83948d0b81338afa/ad6481f49fb2c703efa3a929643934f24b666d6a/f25994f7a9ad53eb756bc4869497c3ebe281ad5e/c091bb49b3233307c7af73dae888f0799752af3d/0ad07e02be0d3f0d554653382ffe53ae4879378d/c4a413e56d16a2ae84e6d8992f215c4dcc7fac20 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (279759) and CERT Bund (WID-SEC-2025-2929). Be aware that VulDB is the high quality source for vulnerability data.
Affected
- Open Source Linux Kernel
Product
Type
Vendor
Name
Version
- 5.4.242
- 5.10.179
- 5.15.110
- 6.1.0
- 6.1.1
- 6.1.2
- 6.1.3
- 6.1.4
- 6.1.5
- 6.1.6
- 6.1.7
- 6.1.8
- 6.1.9
- 6.1.10
- 6.1.11
- 6.1.12
- 6.1.13
- 6.1.14
- 6.1.15
- 6.1.16
- 6.1.17
- 6.1.18
- 6.1.19
- 6.1.20
- 6.1.21
- 6.1.22
- 6.1.23
- 6.1.24
- 6.1.25
- 6.1.26
- 6.1.27
- 6.2.0
- 6.2.1
- 6.2.2
- 6.2.3
- 6.2.4
- 6.2.5
- 6.2.6
- 6.2.7
- 6.2.8
- 6.2.9
- 6.2.10
- 6.2.11
- 6.2.12
- 6.2.13
- 6.2.14
- 6.3.0
- 6.3.1
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Return valueCWE: CWE-252 / CWE-253
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 279759
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2023-54097
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.4.243/5.10.180/5.15.111/6.1.28/6.2.15/6.3.2
Patch: 824683dbec234a01bd49a0589ee3323594a6f4cf/dfce9bb3517a78507cf96f9b83948d0b81338afa/ad6481f49fb2c703efa3a929643934f24b666d6a/f25994f7a9ad53eb756bc4869497c3ebe281ad5e/c091bb49b3233307c7af73dae888f0799752af3d/0ad07e02be0d3f0d554653382ffe53ae4879378d/c4a413e56d16a2ae84e6d8992f215c4dcc7fac20
Timeline
12/24/2025 Advisory disclosed12/24/2025 CVE reserved
12/24/2025 VulDB entry created
01/03/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-54097 (🔒)
GCVE (CVE): GCVE-0-2023-54097
GCVE (VulDB): GCVE-100-338063
CERT Bund: WID-SEC-2025-2929 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 12/24/2025 15:00Updated: 01/03/2026 00:07
Changes: 12/24/2025 15:00 (60), 12/29/2025 06:00 (2), 01/03/2026 00:07 (7)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.