LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel denial-of-service risk in the WWAN IOSM driver. Under a suspend/resume and device removal/rescan sequence, a failed driver initialization can leave an internal structure unallocated, then the removal path dereferences it and crashes.

Executive priority

Treat this as a targeted availability issue. It is not currently documented as exploited, but affected Linux systems using the relevant WWAN driver should receive normal kernel patching priority, with faster handling for mobile, embedded, or operationally sensitive systems.

Technical view

The flaw is a NULL pointer dereference in the Linux net/wwan/iosm driver. If ipc_imem_wwan_channel_init() fails to obtain valid device capabilities, the wwan structure is not allocated, but ipc_wwan_deinit() can still dereference it during removal. The fix handles return values, releases resources on failure, and reports link-down.

Likely exposure

Exposure appears limited to Linux systems using the IOSM WWAN driver on affected kernel versions listed in the CVE source. The provided data does not identify affected distributions, devices, or cloud images.

Exploitation context

The source bundle does not report active exploitation, public exploit code, or KEV listing. The described trigger involves suspend/resume with device removal and rescan after a driver initialization failure, suggesting local or device-state-dependent denial-of-service conditions rather than remote compromise.

Researcher notes

Evidence is limited to the CVE text and Linux stable commit references. No CVSS, CWE, exploit status, affected distribution mapping, or precise fixed release matrix is provided in the source bundle.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • Check distribution advisories for exact fixed package versions.
  • Prioritize systems using WWAN IOSM functionality or affected kernel builds.
  • If patching is delayed, assess whether affected WWAN functionality can be disabled.
  • Monitor for kernel crash reports during suspend/resume or WWAN device resets.

Validation and detection

  • Inventory Linux kernel versions against the CVE affected-version data.
  • Confirm whether the IOSM WWAN driver is present or in use.
  • Check vendor kernel changelogs for the referenced stable commits.
  • Review crash logs for NULL dereference in IOSM WWAN removal paths.
  • Validate suspend/resume and device rescan behavior after updating.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53561 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3670970dd8c661c10c10c300d726f59428eaad32, 3670970dd8c661c10c10c300d726f59428eaad32, 3670970dd8c661c10c10c300d726f59428eaad32unaffected
LinuxLinux5.14, 0, 6.1.30, 6.3.4, 6.4affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.