CVE-2023-54044

spmi: Add a check for remove callback when removing a SPMI driver

N/A
Published: December 24, 2025 at 12:22 PM UTC
Updated: June 17, 2026 at 06:46 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.3%

Description

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 observed when removing the QCOM SPMI PMIC driver: dump_backtrace.cfi_jt+0x0/0x8 dump_stack_lvl+0xd8/0x16c panic+0x188/0x498 __cfi_slowpath+0x0/0x214 __cfi_slowpath+0x1dc/0x214 spmi_drv_remove+0x16c/0x1e0 device_release_driver_internal+0x468/0x79c driver_detach+0x11c/0x1a0 bus_remove_driver+0xc4/0x124 driver_unregister+0x58/0x84 cleanup_module+0x1c/0xc24 [qcom_spmi_pmic] __do_sys_delete_module+0x3ec/0x53c __arm64_sys_delete_module+0x18/0x28 el0_svc_common+0xdc/0x294 el0_svc+0x38/0x9c el0_sync_handler+0x8c/0xf0 el0_sync+0x1b4/0x1c0 If a driver has all its resources allocated through devm_() APIs and does not need any other explicit cleanup, it would not require a remove callback to be defined. Hence, add a check for remove callback presence before calling it when removing a SPMI driver.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.15 ≤ v < 4.14.3153.15 ≤ v < 4.19.2833.15 ≤ v < 5.10.1803.15 ≤ v < 5.15.1113.15 ≤ v < 5.4.2433.15 ≤ v < 6.1.283.15 ≤ v < 6.2.153.15 ≤ v < 6.3.23.15 ≤ v < 6.43.155a86bf343976b9c8ab2f240bc866451fa67e5573
Vendor states this is fixed in 0f3ef30c1c05502f5de3b73b3715d5994845c1b4 (fixed)
Vendor states this is fixed in 428cc252701d6864151f3a296ffc23e1e49a7408 (fixed)
Vendor states this is fixed in 54dda732225555dc6d660e95793c54a0a44b612c (fixed)
Vendor states this is fixed in 699949219e35fe29fd42ccf8cd92c989c3d15109 (fixed)
Vendor states this is fixed in af763c29b9e7040fedd0077bca053b101438a3a4 (fixed)
Vendor states this is fixed in b56eef3e16d888883fefab47425036de80dd38fc (fixed)
Vendor states this is fixed in b95a69214daea4aab1c8bad96571d988a62e2c97 (fixed)
Vendor states this is fixed in c45ab3ab9c371c9ac22bbe1217e5abb2e55a3d4b (fixed)
Vendor states this is fixed in ee0b6146317a98bfec848d7bde5586beb245a38f (fixed)
Vendor states this is fixed in 3.15 (unaffected)
Vendor states this is fixed in 4.14.315 (unaffected)
Vendor states this is fixed in 4.19.283 (unaffected)
Vendor states this is fixed in 5.10.180 (unaffected)
Vendor states this is fixed in 5.15.111 (unaffected)
Vendor states this is fixed in 5.4.243 (unaffected)
Vendor states this is fixed in 6.1.28 (unaffected)
Vendor states this is fixed in 6.2.15 (unaffected)
Vendor states this is fixed in 6.3.2 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card