CVE-2023-54044

In the Linux kernel, the following vulnerability has been resolved: spmi: Add a check for remove callback when removing a SPMI driver When removing a SPMI driver, there can be a crash due to NULL pointer dereference if it does not have a remove callback defined. This is one such call trace observ...

UBUNTU-CVE-2023-54097

In the Linux kernel, the following vulnerability has been resolved: regulator: stm32-pwr: fix ofiomap leak Smatch reports: drivers/regulator/stm32-pwr.c:166 stm32pwrregulatorprobe warn: 'base' from ofiomap not released on lines: 151,166. In stm32pwrregulatorprobe, base is not released when...

CVE-2023-54097 regulator: stm32-pwr: fix of_iomap leak

In the Linux kernel, the following vulnerability has been resolved: regulator: stm32-pwr: fix ofiomap leak Smatch reports: drivers/regulator/stm32-pwr.c:166 stm32pwrregulatorprobe warn: 'base' from ofiomap not released on lines: 151,166. In stm32pwrregulatorprobe, base is not released when...

CVE-2023-54097

CVE-2023-54097 (Linux kernel) affects the regulator subsystem, specifically the stm32-pwr regulator driver. The issue is an of_iomap() leak in stm32_pwr_regulator_probe() that can leak the mapped base address if memory allocation or regulator registration fails. The fix replaces of_iomap() with d...

CVE-2023-54044

Technical details about CVE-2023-54044 (Linux spmi remove callback crash) are not publicly provided in the supplied documents; monitor for updates.

CVE-2023-54044 spmi: Add a check for remove callback when removing a SPMI driver

In the Linux kernel, the following vulnerability has been resolved: spmi: Add a check for remove callback when removing a SPMI driver When removing a SPMI driver, there can be a crash due to NULL pointer dereference if it does not have a remove callback defined. This is one such call trace observ...

PT-2025-53174

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contains a memory leak in the stm32-pwr regulator driver. Specifically, the of iomap function in stm32 pwr regulator probe does not release allocated memory when devm...

SUSE CVE-2025-68172

In the Linux kernel, the following vulnerability has been resolved: crypto: aspeed - fix double free caused by devm The clock obtained via devmclkgetenabled is automatically managed by devres and will be disabled and freed on driver detach. Manually calling clkdisableunprepare in error path and...

EUVD-2025-203726

In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Do not kfree devres managed rdev Since the allocation of the drivers main structure was changed to devmdrmdevalloc rdev is managed by devres and we shouldn't be calling kfree on it. This fixes things exploding if the...

EUVD-2025-203715

In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Remove calls to drmputdev Since the allocation of the drivers main structure was changed to devmdrmdevalloc drmputdev'ing to trigger it to be free'd should be done by devres. However, drmputdev is still in the probe...

EUVD-2025-203724

In the Linux kernel, the following vulnerability has been resolved: crypto: aspeed - fix double free caused by devm The clock obtained via devmclkgetenabled is automatically managed by devres and will be disabled and freed on driver detach. Manually calling clkdisableunprepare in error path and...

CVE-2025-68181

In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Remove calls to drmputdev Since the allocation of the drivers main structure was changed to devmdrmdevalloc drmputdev'ing to trigger it to be free'd should be done by devres. However, drmputdev is still in the probe...

CVE-2025-68172

In the Linux kernel, the following vulnerability has been resolved: crypto: aspeed - fix double free caused by devm The clock obtained via devmclkgetenabled is automatically managed by devres and will be disabled and freed on driver detach. Manually calling clkdisableunprepare in error path and...

CVE-2025-68172

In the Linux kernel, the following vulnerability has been resolved: crypto: aspeed - fix double free caused by devm The clock obtained via devmclkgetenabled is automatically managed by devres and will be disabled and freed on driver detach. Manually calling clkdisableunprepare in error path and...

CVE-2025-68193

In the Linux kernel, the following vulnerability has been resolved: drm/xe/guc: Add devm release action to safely tear down CT When a buffer object BO is allocated with the XEBOFLAGGGTTINVALIDATE flag, the driver initiates TLB invalidation requests via the CTB mechanism while releasing the BO...

CVE-2025-68222

CVE-2025-68222 (Linux kernel) : The pinctrl driver for the NXP S32CC PHY/SoC allocated s32_pinctrl_desc with devm_kmalloc() but did not initialize all fields (notably num_custom_params), causing intermittent allocation failures during pinctrl/DT parsing, which in turn can cascade to parse errors ...

CVE-2025-68193 drm/xe/guc: Add devm release action to safely tear down CT

In the Linux kernel, the following vulnerability has been resolved: drm/xe/guc: Add devm release action to safely tear down CT When a buffer object BO is allocated with the XEBOFLAGGGTTINVALIDATE flag, the driver initiates TLB invalidation requests via the CTB mechanism while releasing the BO...

PT-2025-51583

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contains a flaw in the DRM/Radeon driver where the rdev structure, managed by devres, was incorrectly being freed using kfree. This occurred because the allocation metho...

CVE-2023-53807

In the Linux kernel, the following vulnerability has been resolved: clk: clocking-wizard: Fix Oops in clkwzrdregisterdivider Smatch detected this potential error pointer dereference clkwzrdregisterdivider. If devmclkhwregister fails then it sets "hw" to an error pointer and then dereferences it o...

CVE-2023-53854

In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8186: Fix use-after-free in driver remove path When devm runs function in the "remove" path for a device it runs them in the reverse order. That means that if you have parts of your driver that aren't using devm...