LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49396: phy: qcom-qmp: fix reset-controller leak on probe errors

In the Linux kernel, the following vulnerability has been resolved: phy: qcom-qmp: fix reset-controller leak on probe errors Make sure to release the lane reset controller in case of a late probe error (e.g. probe deferral). Note that due to the reset controller being defined in devicetree in "lane" child nodes, devm_reset_control_get_exclusive() cannot be used directly.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel driver cleanup flaw in Qualcomm QMP PHY handling. If device probing fails late, such as during probe deferral, the driver may leak a lane reset controller reference. The available sources do not show active exploitation, CVSS scoring, or broad business impact details.

Executive priority

Treat this as routine kernel maintenance unless affected Qualcomm-based devices show stability problems. There is no cited active exploitation or severity score, but kernel fixes should be folded into normal patch cycles.

Technical view

The qcom-qmp PHY driver failed to release the lane reset controller on late probe errors. The fix explicitly releases that controller because the reset controller is defined under devicetree lane child nodes and cannot use devm_reset_control_get_exclusive() directly.

Likely exposure

Exposure appears limited to Linux systems using the Qualcomm QMP PHY driver, especially Qualcomm-based platforms where probe errors or deferrals occur. The source lists Linux as affected and names several kernel version lines, but provides no CPEs or product-specific distribution mapping.

Exploitation context

No KEV listing is present, and the provided sources do not claim active exploitation. The described trigger is a driver probe error path, not a documented remote attack path. Impact evidence is incomplete beyond a reset-controller resource leak.

Researcher notes

Focus validation on the qcom-qmp probe error path and reset controller lifecycle. The evidence supports a leak on late probe failure, but does not provide exploit primitives, attacker requirements, or distribution-specific affected package versions.

Mitigation direction

  • Update to a kernel containing the referenced stable qcom-qmp fix.
  • Check Linux distribution or device vendor advisories for backported fixes.
  • Prioritize Qualcomm-based devices using the qcom-qmp PHY driver.
  • Review vendor guidance before applying unsupported kernel changes.

Validation and detection

  • Inventory Linux kernel versions on Qualcomm-based systems.
  • Confirm whether the qcom-qmp PHY driver is present and enabled.
  • Check whether vendor kernels include one of the referenced fixes or a backport.
  • Review boot and kernel logs for qcom-qmp probe deferral or probe failures.
Prepared
Confidence
medium
Sources
10

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-2022-49396 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
9Source 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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe78f3d15e115e8e764d4b1562b4fa538f2e22f6b, e78f3d15e115e8e764d4b1562b4fa538f2e22f6b, e78f3d15e115e8e764d4b1562b4fa538f2e22f6b, e78f3d15e115e8e764d4b1562b4fa538f2e22f6b, e78f3d15e115e8e764d4b1562b4fa538f2e22f6b, e78f3d15e115e8e764d4b1562b4fa538f2e22f6b, e78f3d15e115e8e764d4b1562b4fa538f2e22f6b, e78f3d15e115e8e764d4b1562b4fa538f2e22f6bunaffected
LinuxLinux4.12, 0, 4.14.283, 4.19.247, 5.4.198, 5.10.121, 5.15.46, 5.17.14, 5.18.3, 5.19affected
Weakness

CWE details

No CWE listed

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