Device-node reference leak via failed bridge binding
Published Jun 18, 2025 · Updated May 11, 2026
A reference-count leak in the Linux MCDE display driver allows local users to retain device-node references via unspecified vectors. The mcde_dsi_bind function returns after of_drm_find_bridge fails without calling of_node_put on the child acquired by for_each_available_child_of_node. Reachability requires an MCDE-equipped Ux500 system and a DSI child whose bridge lookup fails; published sources do not establish how a local user triggers that state or a resulting service impact.
Summary
What happened
A reference-count leak in the Linux MCDE display driver allows local users to retain device-node references via unspecified vectors. The mcde_dsi_bind function returns after of_drm_find_bridge fails without calling of_node_put on the child acquired by for_each_available_child_of_node. Reachability requires an MCDE-equipped Ux500 system and a DSI child whose bridge lookup fails; published sources do not establish how a local user triggers that state or a resulting service impact.
The record
- CVE
- CVE-2022-50176
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.3
- Affected versionversion=5fc537bfd00033a3f813330175f7f12c25957ebf <3123ae6fdd4013d24a3a4877084b14e917faae5c
- Affected versionversion=5fc537bfd00033a3f813330175f7f12c25957ebf <32c827e30bb44ae809950a9efab59e98e44d30e5
- Affected versionversion=5fc537bfd00033a3f813330175f7f12c25957ebf <3a149169e4a2f9127022fec6ef5d71b4e804b3b9
- Affected versionversion=5fc537bfd00033a3f813330175f7f12c25957ebf <7214902de5b1fb2b632a7b8b3b9540e41aabab38
- Affected versionversion=5fc537bfd00033a3f813330175f7f12c25957ebf <87c35bbefdfa3c5edfb8c80f5c04717aaacc629d
- Affected versionversion=5fc537bfd00033a3f813330175f7f12c25957ebf <f57699a9b66ea11f000f56d1f1179059239b8690
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo