Strix
26.1K

CVE-2023-54097

UnknownEPSS 0.18%

Last modified

CVE-2023-54097 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.18% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.18%

7.8th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= dc62f951a6a8490bcccc7b6de36cd85bd57be740, < 824683dbec234a01bd49a0589ee3323594a6f4cf; >= dc62f951a6a8490bcccc7b6de36cd85bd57be740, < dfce9bb3517a78507cf96f9b83948d0b81338afa; >= dc62f951a6a8490bcccc7b6de36cd85bd57be740, < ad6481f49fb2c703efa3a929643934f24b666d6a; >= dc62f951a6a8490bcccc7b6de36cd85bd57be740, < f25994f7a9ad53eb756bc4869497c3ebe281ad5e; >= dc62f951a6a8490bcccc7b6de36cd85bd57be740, < c091bb49b3233307c7af73dae888f0799752af3d; >= dc62f951a6a8490bcccc7b6de36cd85bd57be740, < 0ad07e02be0d3f0d554653382ffe53ae4879378d; >= dc62f951a6a8490bcccc7b6de36cd85bd57be740, < c4a413e56d16a2ae84e6d8992f215c4dcc7fac20
LinuxLinux5.2

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2023-54097?
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.
How severe is CVE-2023-54097?
Severity scoring for CVE-2023-54097 is pending analysis. The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2023-54097?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2023

View all 2023CVEs →

Are you affected by CVE-2023-54097?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST