regulator: stm32-pwr: fix of_iomap leak
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.2
References 7
git.kernel.org
- stable/c/824683dbec234a01bd49a0589ee3323594a6f4cf
- stable/c/dfce9bb3517a78507cf96f9b83948d0b81338afa
- stable/c/ad6481f49fb2c703efa3a929643934f24b666d6a
- stable/c/f25994f7a9ad53eb756bc4869497c3ebe281ad5e
- stable/c/c091bb49b3233307c7af73dae888f0799752af3d
- stable/c/0ad07e02be0d3f0d554653382ffe53ae4879378d
- stable/c/c4a413e56d16a2ae84e6d8992f215c4dcc7fac20