CVE-2023-54044

Not scored yetLast modified Jun 17, 2026

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.

Metrics

No CVSS score has been published yet.

Affected software

VendorProductVersions
LinuxLinux>= 5a86bf343976b9c8ab2f240bc866451fa67e5573, < b95a69214daea4aab1c8bad96571d988a62e2c97; >= 5a86bf343976b9c8ab2f240bc866451fa67e5573, < 699949219e35fe29fd42ccf8cd92c989c3d15109; >= 5a86bf343976b9c8ab2f240bc866451fa67e5573, < 54dda732225555dc6d660e95793c54a0a44b612c; >= 5a86bf343976b9c8ab2f240bc866451fa67e5573, < c45ab3ab9c371c9ac22bbe1217e5abb2e55a3d4b; >= 5a86bf343976b9c8ab2f240bc866451fa67e5573, < ee0b6146317a98bfec848d7bde5586beb245a38f; >= 5a86bf343976b9c8ab2f240bc866451fa67e5573, < 428cc252701d6864151f3a296ffc23e1e49a7408; >= 5a86bf343976b9c8ab2f240bc866451fa67e5573, < af763c29b9e7040fedd0077bca053b101438a3a4; >= 5a86bf343976b9c8ab2f240bc866451fa67e5573, < 0f3ef30c1c05502f5de3b73b3715d5994845c1b4; >= 5a86bf343976b9c8ab2f240bc866451fa67e5573, < b56eef3e16d888883fefab47425036de80dd38fc
LinuxLinux3.15

References

Timeline

Published
Dec 24, 2025
Last modified
Jun 17, 2026
NVD status
Deferred

Related CVEs from 2023

CVE-2023-54045In the Linux kernel, the following vulnerability has been resolved: audit: fix possible soft lockup in __audit_inode_child() Tracefs or deCVE-2023-540467.8In the Linux kernel, the following vulnerability has been resolved: crypto: essiv - Handle EBUSY correctly As it is essiv only handles theCVE-2023-54047In the Linux kernel, the following vulnerability has been resolved: drm/rockchip: dw_hdmi: cleanup drm encoder during unbind This fixes a CVE-2023-540487.8In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Prevent handling any completions after qp destroy HW mayCVE-2023-54049In the Linux kernel, the following vulnerability has been resolved: rpmsg: glink: Add check for kstrdup Add check for the return value of CVE-2023-54055.9Server information leak for the CDA Server process memory can occur when an error is generated in response to a specially crafted message. SCVE-2023-540507.8In the Linux kernel, the following vulnerability has been resolved: ubifs: Fix memleak when insert_old_idx() failed Following process willCVE-2023-54051In the Linux kernel, the following vulnerability has been resolved: net: do not allow gso_size to be set to GSO_BY_FRAGS One missing checkCVE-2023-54052In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7921: fix skb leak by txs missing in AMSDU txs may be drCVE-2023-54053In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: pcie: fix possible NULL pointer dereference It is possiCVE-2023-54055In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Fix memory leak of PBLE objects On rmmod of irdma, the PBLCVE-2023-54056In the Linux kernel, the following vulnerability has been resolved: kheaders: Use array declaration instead of char Under CONFIG_FORTIFY_S
CVE-2023-54044: Unscored | Vulnix