In the Linux kernel, the following vulnerability has been resolved:
drm/msm/dp: fix bridge lifetime
Device-managed resources allocated post component bind must be tied to
the lifetime of the aggregate DRM device or they will not necessarily be
released when binding of the aggregate device is deferred.
This can lead resource leaks or failure to bind the aggregate device
when binding is later retried and a second attempt to allocate the
resources is made.
For the DP bridges, previously allocated bridges will leak on probe
deferral.
Fix this by amending the DP parser interface and tying the lifetime of
the bridge device to the DRM device rather than DP platform device.
Patchwork: https://patchwork.freedesktop.org/patch/502667/
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects Qualcomm MSM DisplayPort bridge handling. Under probe deferral, previously allocated bridge resources can leak and later prevent the combined DRM display device from binding. The source describes reliability and resource-management impact, not data theft or remote compromise.
Executive priority
Treat this as a targeted kernel maintenance item, not an emergency, unless affected devices show display or DRM initialization failures. Current evidence does not support active exploitation or broad business compromise.
Technical view
The drm/msm/dp code tied post-bind device-managed bridge resources to the DP platform device rather than the aggregate DRM device. If aggregate binding was deferred, DP bridges could leak; a retry could fail when allocating the same resources again. The fix changes the DP parser interface and bridge lifetime ownership.
Likely exposure
Exposure appears limited to Linux systems using affected kernel versions with the MSM DRM DisplayPort path, typically Qualcomm-based platforms. The bundle lists affected Linux versions including 5.19, 6.0.7, and 6.1, but product and distribution mappings are not provided.
Exploitation context
No CISA KEV listing, exploit report, CVSS score, attack vector, or exploitability detail is provided in the source bundle. The described failure mode is probe deferral causing resource leaks or DRM aggregate device bind failure.
Researcher notes
Evidence is narrow: no CVSS, CWE, exploitability assessment, or distribution-specific status is included. The primary research focus is confirming affected kernel ranges, whether the msm DP driver is enabled, and whether stable fixes are backported.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Check Linux distribution advisories for backported fixes to supported kernels.
Prioritize affected Qualcomm MSM DisplayPort systems with display initialization failures.
Avoid inventing workarounds; follow kernel or distribution guidance.
Validation and detection
Inventory deployed kernel versions and Qualcomm MSM DisplayPort usage.
Check kernel package changelogs for the referenced stable commit IDs.
Review boot logs for DRM/MSM DP probe deferral or bind failures.
Confirm vendor advisories map your kernel build to a fixed release.
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-50292 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
3Source 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.
Sep 15, 2025, 14:45 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.