CVE-2023-53551: usb: gadget: u_serial: Add null pointer check in gserial_resume
In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: u_serial: Add null pointer check in gserial_resume
Consider a case where gserial_disconnect has already cleared
gser->ioport. And if a wakeup interrupt triggers afterwards,
gserial_resume gets called, which will lead to accessing of
gser->ioport and thus causing null pointer dereference.Add
a null pointer check to prevent this.
Added a static spinlock to prevent gser->ioport from becoming
null after the newly added check.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash systems using the USB gadget serial driver when a resume event occurs after disconnect cleanup. The source describes a null pointer dereference, so the likely business impact is availability, not data theft. Public evidence does not show active exploitation or a CVSS score.
Executive priority
Treat as a targeted availability risk for Linux-based devices using USB gadget serial. Prioritize patch validation on embedded, appliance, and physically accessible systems rather than broad emergency response, unless vendor advisories raise severity.
Technical view
In usb gadget u_serial, gserial_disconnect can clear gser->ioport before gserial_resume runs after a wakeup interrupt. The fix adds a null pointer check and a static spinlock so ioport cannot become null after validation. Affected Linux kernel versions are listed in the CVE record, with fixes referenced in stable commits.
Likely exposure
Exposure is most likely on Linux systems or embedded devices that enable USB gadget serial functionality. General-purpose servers without this driver or USB gadget use are less likely exposed, but kernel configuration and package version must be verified.
Exploitation context
The bundle does not cite KEV listing, public exploitation, exploit code, or attacker prerequisites. The described failure mode is a race-like resume-after-disconnect condition leading to null pointer dereference and probable denial of service.
Researcher notes
Evidence is limited to the CVE record and Linux stable commits. The core issue is a null dereference prevented by pointer validation and locking. No CWE, CVSS, exploitability assessment, or confirmed attack path is provided in the bundle.
Mitigation direction
Update affected Linux kernels using vendor-supported packages or referenced stable fixes.
Check Linux distribution advisories for backported fixes before relying on upstream version numbers.
Prioritize embedded and USB gadget-enabled devices in remediation planning.
Disable unused USB gadget serial functionality where operationally feasible.
Monitor vendor guidance for severity, CVSS, and affected configuration clarification.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and embedded devices.
Check whether USB gadget serial support is built in or loaded as a module.
Map installed kernels against vendor advisories and the CVE affected-version data.
Confirm patched builds include the referenced u_serial gserial_resume fix.
Review crash logs for null pointer dereferences involving gserial_resume or u_serial.
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-53551 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
6Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Oct 4, 2025, 15:16 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.