linux-cve-announce - CVE-2023-53561: net: wwan: iosm: fix NULL pointer dereference when removing device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025100450-CVE-2023-53561-75a1@gregkh>
Date: Sat,  4 Oct 2025 17:17:15 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53561: net: wwan: iosm: fix NULL pointer dereference when removing device

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

net: wwan: iosm: fix NULL pointer dereference when removing device

In suspend and resume cycle, the removal and rescan of device ends
up in NULL pointer dereference.

During driver initialization, if the ipc_imem_wwan_channel_init()
fails to get the valid device capabilities it returns an error and
further no resource (wwan struct) will be allocated. Now in this
situation if driver removal procedure is initiated it would result
in NULL pointer exception since unallocated wwan struct is dereferenced
inside ipc_wwan_deinit().

ipc_imem_run_state_worker() to handle the called functions return value
and to release the resource in failure case. It also reports the link
down event in failure cases. The user space application can handle this
event to do a device reset for restoring the device communication.

The Linux kernel CVE team has assigned CVE-2023-53561 to this issue.

Affected and fixed versions
===========================

	Issue introduced in 5.14 with commit 3670970dd8c661c10c10c300d726f59428eaad32 and fixed in 6.1.30 with commit ee44bacf462db3ec6e4f0dcfa7931e768670d77c
	Issue introduced in 5.14 with commit 3670970dd8c661c10c10c300d726f59428eaad32 and fixed in 6.3.4 with commit 862c6e3e26735247d8a4df41fa2421909c3f4d63
	Issue introduced in 5.14 with commit 3670970dd8c661c10c10c300d726f59428eaad32 and fixed in 6.4 with commit 60829145f1e2650b31ebe6a0ec70a9725b38fa2c

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2023-53561
will be updated if fixes are backported, please check that for the most
up to date information about this issue.

Affected files
==============

The file(s) affected by this issue are:
	drivers/net/wwan/iosm/iosm_ipc_imem.c
	drivers/net/wwan/iosm/iosm_ipc_imem_ops.c
	drivers/net/wwan/iosm/iosm_ipc_imem_ops.h

Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/ee44bacf462db3ec6e4f0dcfa7931e768670d77c
	https://git.kernel.org/stable/c/862c6e3e26735247d8a4df41fa2421909c3f4d63
	https://git.kernel.org/stable/c/60829145f1e2650b31ebe6a0ec70a9725b38fa2c