CVE-2023-53379: usb: phy: phy-tahvo: fix memory leak in tahvo_usb_probe()
In the Linux kernel, the following vulnerability has been resolved:
usb: phy: phy-tahvo: fix memory leak in tahvo_usb_probe()
Smatch reports:
drivers/usb/phy/phy-tahvo.c: tahvo_usb_probe()
warn: missing unwind goto?
After geting irq, if ret < 0, it will return without error handling to
free memory.
Just add error handling to fix this problem.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in the Tahvo USB PHY driver. A local, low-privileged user could potentially trigger availability impact on systems using affected kernels and this driver path. It is not described as remote code execution or data theft.
Executive priority
Handle through the standard kernel patch program, with faster action for exposed operational systems that match the affected kernels and driver path. Business urgency is moderate because the stated impact is availability and local access is required.
Technical view
In tahvo_usb_probe(), an error path after IRQ acquisition can return without freeing allocated memory. The CVE maps to CWE-401 and CVSS 3.1 score 5.5, with local access, low complexity, low privileges, no user interaction, and high availability impact.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel versions where the phy-tahvo USB PHY driver code is present or used. The supplied data lists affected Linux kernel version ranges and stable commit references but does not identify specific distributions or appliances.
Exploitation context
The source bundle marks KEV as false and provides no evidence of active exploitation. The CVSS vector is local and low-privileged, with no confidentiality or integrity impact stated. Treat this as an availability-risk kernel defect, not a confirmed exploited issue.
Researcher notes
Evidence supports a memory-leak error-unwind bug in drivers/usb/phy/phy-tahvo.c. The bundle provides upstream stable fix references but not distribution package names, real-world exploitation, or standalone mitigations. Validate distro backports and driver reachability before scoring local exposure.
Mitigation direction
Update affected Linux kernels using vendor-supported packages or stable releases containing the referenced fixes.
Prioritize systems matching affected kernel versions and using the Tahvo USB PHY driver path.
Check distribution advisories for backported fixes before relying only on upstream version numbers.
Plan reboot or live-patching according to normal kernel maintenance procedures.
Monitor the CVE record and Linux stable references for updated affected-version guidance.
Validation and detection
Inventory running Linux kernel versions against the affected and fixed version data in the CVE record.
Confirm whether the phy-tahvo driver code is built, packaged, or used on relevant systems.
Review vendor kernel changelogs for the referenced stable fix commits or equivalent backports.
After updating, verify systems run the remediated kernel build.
Include availability regression checks for systems that depend on USB PHY functionality.
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.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.