summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorGuangshuo Li <lgs201920130244@gmail.com>2026-05-05 12:12:31 +0300
committerDanilo Krummrich <dakr@kernel.org>2026-05-07 01:44:52 +0300
commit896df22ee57648b0c505bd76ddbc6b2341834696 (patch)
tree0cfdc8439330655e258419b28cf237902c18e3a5 /include/linux
parent30c878ed169983190f77940594f8ba8948debe6b (diff)
downloadlinux-896df22ee57648b0c505bd76ddbc6b2341834696.tar.xz
firmware_loader: fix device reference leak in firmware_upload_register()
firmware_upload_register() -> fw_create_instance() -> device_initialize() After fw_create_instance() succeeds, the lifetime of the embedded struct device is expected to be managed through the device core reference counting, since fw_create_instance() has already called device_initialize(). In firmware_upload_register(), if alloc_lookup_fw_priv() fails after fw_create_instance() succeeds, the code reaches free_fw_sysfs and frees fw_sysfs directly instead of releasing the device reference with put_device(). This may leave the reference count of the embedded struct device unbalanced, resulting in a refcount leak. The issue was identified by a static analysis tool I developed and confirmed by manual review. Fix this by using put_device(fw_dev) in the failure path and letting fw_dev_release() handle the final cleanup, instead of freeing the instance directly from the error path. Fixes: 97730bbb242c ("firmware_loader: Add firmware-upload support") Cc: stable@vger.kernel.org Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com> Link: https://patch.msgid.link/20260505091231.607089-1-lgs201920130244@gmail.com Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions